MITRE ATT&CK T1418: Software Discovery
When to use this skill
Use this skill when the task involves T1418, Software Discovery, mobile ATT&CK, TTP mapping, detection engineering, hunting, incident-response enrichment, control validation, or authorized adversary-emulation planning. Treat it as a defensive analysis aid: keep outputs focused on understanding, detecting, mitigating, and safely validating this ATT&CK technique.
Technique context
- ATT&CK domain: mobile
- ATT&CK ID: T1418
- Technique name: Software Discovery
- Type: technique
- ATT&CK URL: https://attack.mitre.org/techniques/T1418
- Tactics: discovery
- Platforms: Android, iOS
- Required permissions: Not specified
- Effective permissions: Not specified
- Defenses bypassed: Not specified
ATT&CK description
Adversaries may attempt to get a listing of applications that are installed on a device. Adversaries may use the information from Software Discovery during automated discovery to shape follow-on behaviors, including whether or not to fully infect the target and/or attempts specific actions.
Adversaries may attempt to enumerate applications for a variety of reasons, such as figuring out what security measures are present or to identify the presence of target applications.
Agent workflow
- Clarify scope: identify the system, asset class, log sources, cloud or endpoint platform, and whether the user wants triage, detection, coverage assessment, or safe emulation planning.
- Load bundled resources as needed: use
references/technique-profile.json for structured metadata, references/detection-and-mitigation.md for triage and telemetry guidance, references/known-threat-context.md for ATT&CK relationship context, and templates/ for repeatable outputs.
- Map observations to ATT&CK: compare the user's evidence to the ATT&CK description, tactics, platforms, and known procedure patterns before asserting a match.
- Produce defensive outputs: prioritize hypotheses, telemetry requirements, detection logic ideas, validation steps, containment guidance, and mitigations.
- Preserve uncertainty: distinguish confirmed evidence, plausible indicators, assumptions, and gaps. Recommend what to collect next.
- Stay safe: do not provide malware, credential theft, persistence, evasion, destructive automation, or unauthorized exploitation instructions. For adversary emulation, keep steps bounded to approved lab or control-validation contexts and omit operational abuse details.
Bundled resources
references/technique-profile.json: machine-readable ATT&CK metadata for this technique.
references/detection-and-mitigation.md: detection notes, telemetry checklist, triage questions, mitigation candidates, and false-positive considerations.
references/known-threat-context.md: ATT&CK relationship context with attribution cautions.
templates/detection-brief.md: detection engineering brief template.
templates/hunt-plan.md: threat hunt plan template.
templates/incident-response-note.md: incident response note template.
templates/coverage-assessment.md: ATT&CK coverage assessment template.
scripts/render_brief.py: local helper that renders a Markdown defensive brief from technique-profile.json.
assets/output-schema.json: JSON schema for structured technique analysis outputs.
To generate a quick brief, run python scripts/render_brief.py --output brief.md from inside this skill directory, or adapt the templates directly.
Detection guidance
No ATT&CK detection guidance was present in the source STIX object.
Useful telemetry and data sources
- Not specified in the STIX object.
Mitigations to consider
- Use Recent OS Version
- User Guidance
Known threat context
Use these examples only as contextual leads, not as proof that an observed event is this technique:
- AbstractEmu (malware)
- Agent Smith (malware)
- Android/AdDisplay.Ashas (malware)
- Anubis (malware)
- BOULDSPY (malware)
- Binary Validator (malware)
- C0033 (campaign)
- CarbonSteal (malware)
- Cerberus (malware)
- Chameleon (malware)
- CherryBlos (malware)
- Crocodilus (malware)
- DEFENSOR ID (malware)
- Desert Scorpion (malware)
- DocSwap (malware)
- DoubleAgent (malware)
- EventBot (malware)
- Exodus (malware)
- FakeSpy (malware)
- FlexiSpy (tool)
Recommended output pattern
When responding with this skill, structure the answer as:
- Assessment: whether the evidence supports this ATT&CK mapping and why.
- Evidence: specific indicators, logs, behaviors, and assumptions.
- Detection: telemetry sources, analytic logic, and tuning considerations.
- Response: containment, eradication, recovery, and validation actions.
- Coverage gaps: missing logs, sensors, controls, or environmental details.
- References: include the ATT&CK URL and any user-provided evidence references.
1---2name: attack-mob-t1418-software-discovery3description: "Analyze MITRE ATT&CK T1418 Software Discovery in the mobile matrix. Use for TTP triage, detection engineering, hunting, defensive emulation planning, mitigations, incident response mapping, ATT&CK coverage, or questions mentioning T1418, Software Discovery, or mobile ATT&CK. Adversaries may attempt to get a listing of applications that are installed on a device."4license: MITRE ATT&CK Terms of Use apply to ATT&CK-derived content. See https://attack.mitre.org/resources/terms-of-use/5metadata:6 source: https://skillmd.com/skills/santosomar/attack-mob-t1418-software-discovery7 upstream: mitre-attack/attack-stix-data8 domain: mobile9 attack_id: T141810 attack_stix_id: attack-pattern--198ce408-1470-45ee-b47f-7056050d4fc211 attack_version: "2.1"12 attack_modified: "2025-10-24T17:48:27.789Z"13---1415# MITRE ATT&CK T1418: Software Discovery1617## When to use this skill1819Use this skill when the task involves T1418, Software Discovery, mobile ATT&CK, TTP mapping, detection engineering, hunting, incident-response enrichment, control validation, or authorized adversary-emulation planning. Treat it as a defensive analysis aid: keep outputs focused on understanding, detecting, mitigating, and safely validating this ATT&CK technique.2021## Technique context2223- ATT&CK domain: mobile24- ATT&CK ID: T141825- Technique name: Software Discovery26- Type: technique27- ATT&CK URL: https://attack.mitre.org/techniques/T141828- Tactics: discovery29- Platforms: Android, iOS30- Required permissions: Not specified31- Effective permissions: Not specified32- Defenses bypassed: Not specified3334## ATT&CK description3536Adversaries may attempt to get a listing of applications that are installed on a device. Adversaries may use the information from [Software Discovery](https://attack.mitre.org/techniques/T1418) during automated discovery to shape follow-on behaviors, including whether or not to fully infect the target and/or attempts specific actions. 3738 3940Adversaries may attempt to enumerate applications for a variety of reasons, such as figuring out what security measures are present or to identify the presence of target applications.4142## Agent workflow43441. Clarify scope: identify the system, asset class, log sources, cloud or endpoint platform, and whether the user wants triage, detection, coverage assessment, or safe emulation planning.452. Load bundled resources as needed: use `references/technique-profile.json` for structured metadata, `references/detection-and-mitigation.md` for triage and telemetry guidance, `references/known-threat-context.md` for ATT&CK relationship context, and `templates/` for repeatable outputs.463. Map observations to ATT&CK: compare the user's evidence to the ATT&CK description, tactics, platforms, and known procedure patterns before asserting a match.474. Produce defensive outputs: prioritize hypotheses, telemetry requirements, detection logic ideas, validation steps, containment guidance, and mitigations.485. Preserve uncertainty: distinguish confirmed evidence, plausible indicators, assumptions, and gaps. Recommend what to collect next.496. Stay safe: do not provide malware, credential theft, persistence, evasion, destructive automation, or unauthorized exploitation instructions. For adversary emulation, keep steps bounded to approved lab or control-validation contexts and omit operational abuse details.5051## Bundled resources5253- `references/technique-profile.json`: machine-readable ATT&CK metadata for this technique.54- `references/detection-and-mitigation.md`: detection notes, telemetry checklist, triage questions, mitigation candidates, and false-positive considerations.55- `references/known-threat-context.md`: ATT&CK relationship context with attribution cautions.56- `templates/detection-brief.md`: detection engineering brief template.57- `templates/hunt-plan.md`: threat hunt plan template.58- `templates/incident-response-note.md`: incident response note template.59- `templates/coverage-assessment.md`: ATT&CK coverage assessment template.60- `scripts/render_brief.py`: local helper that renders a Markdown defensive brief from `technique-profile.json`.61- `assets/output-schema.json`: JSON schema for structured technique analysis outputs.6263To generate a quick brief, run `python scripts/render_brief.py --output brief.md` from inside this skill directory, or adapt the templates directly.6465## Detection guidance6667No ATT&CK detection guidance was present in the source STIX object.6869## Useful telemetry and data sources7071- Not specified in the STIX object.7273## Mitigations to consider7475- Use Recent OS Version76- User Guidance7778## Known threat context7980Use these examples only as contextual leads, not as proof that an observed event is this technique:8182- AbstractEmu (malware)83- Agent Smith (malware)84- Android/AdDisplay.Ashas (malware)85- Anubis (malware)86- BOULDSPY (malware)87- Binary Validator (malware)88- C0033 (campaign)89- CarbonSteal (malware)90- Cerberus (malware)91- Chameleon (malware)92- CherryBlos (malware)93- Crocodilus (malware)94- DEFENSOR ID (malware)95- Desert Scorpion (malware)96- DocSwap (malware)97- DoubleAgent (malware)98- EventBot (malware)99- Exodus (malware)100- FakeSpy (malware)101- FlexiSpy (tool)102103## Recommended output pattern104105When responding with this skill, structure the answer as:106107- Assessment: whether the evidence supports this ATT&CK mapping and why.108- Evidence: specific indicators, logs, behaviors, and assumptions.109- Detection: telemetry sources, analytic logic, and tuning considerations.110- Response: containment, eradication, recovery, and validation actions.111- Coverage gaps: missing logs, sensors, controls, or environmental details.112- References: include the ATT&CK URL and any user-provided evidence references.