MITRE ATT&CK T1655.001: Match Legitimate Name or Location
When to use this skill
Use this skill when the task involves T1655.001, Match Legitimate Name or Location, 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 sub-technique.
Technique context
- ATT&CK domain: mobile
- ATT&CK ID: T1655.001
- Technique name: Match Legitimate Name or Location
- Type: sub-technique
- ATT&CK URL: https://attack.mitre.org/techniques/T1655/001
- Tactics: defense-evasion
- Platforms: Android, iOS
- Required permissions: Not specified
- Effective permissions: Not specified
- Defenses bypassed: Not specified
ATT&CK description
Adversaries may match or approximate the name or location of legitimate files or resources when naming/placing them. This is done for the sake of evading defenses and observation. This may be done by giving artifacts the name and icon of a legitimate, trusted application (i.e., Settings), or using a package name that matches legitimate, trusted applications (i.e., com.google.android.gm).
Adversaries may also use the same icon of the file or application they are trying to mimic.
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
Known threat context
Use these examples only as contextual leads, not as proof that an observed event is this technique:
- APT-C-23 (intrusion-set)
- Agent Smith (malware)
- AndroRAT (malware)
- Android/AdDisplay.Ashas (malware)
- Android/SpyAgent (malware)
- AndroidOS/MalLocker.B (malware)
- Anubis (malware)
- Asacub (malware)
- BOULDSPY (malware)
- BRATA (malware)
- Bouncing Golf (intrusion-set)
- C0033 (campaign)
- CHEMISTGAMES (malware)
- CarbonSteal (malware)
- Cerberus (malware)
- Chameleon (malware)
- DCHSpy (malware)
- Dendroid (malware)
- DocSwap (malware)
- DoubleAgent (malware)
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.
ATT&CK contributors
- Ford Qin, Trend Micro
- Liran Ravich, CardinalOps
1---2name: attack-mob-t1655-001-match-legitimate-name-or-location3description: "Analyze MITRE ATT&CK T1655.001 Match Legitimate Name or Location in the mobile matrix. Use for TTP triage, detection engineering, hunting, defensive emulation planning, mitigations, incident response mapping, ATT&CK coverage, or questions mentioning T1655.001, Match Legitimate Name or Location, or mobile ATT&CK. Adversaries may match or approximate the name or location of legitimate files or resources when naming/placing them."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-t1655-001-match-legitimate-name-or-location7 upstream: mitre-attack/attack-stix-data8 domain: mobile9 attack_id: T1655.00110 attack_stix_id: attack-pattern--114fed8b-7eed-4136-8b9c-411c5c7fff4b11 attack_version: "1.0"12 attack_modified: "2025-04-16T21:21:44.590Z"13---1415# MITRE ATT&CK T1655.001: Match Legitimate Name or Location1617## When to use this skill1819Use this skill when the task involves T1655.001, Match Legitimate Name or Location, 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 sub-technique.2021## Technique context2223- ATT&CK domain: mobile24- ATT&CK ID: T1655.00125- Technique name: Match Legitimate Name or Location26- Type: sub-technique27- ATT&CK URL: https://attack.mitre.org/techniques/T1655/00128- Tactics: defense-evasion29- Platforms: Android, iOS30- Required permissions: Not specified31- Effective permissions: Not specified32- Defenses bypassed: Not specified3334## ATT&CK description3536Adversaries may match or approximate the name or location of legitimate files or resources when naming/placing them. This is done for the sake of evading defenses and observation. This may be done by giving artifacts the name and icon of a legitimate, trusted application (i.e., Settings), or using a package name that matches legitimate, trusted applications (i.e., `com.google.android.gm`). 3738Adversaries may also use the same icon of the file or application they are trying to mimic.3940## Agent workflow41421. 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.432. 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.443. 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.454. Produce defensive outputs: prioritize hypotheses, telemetry requirements, detection logic ideas, validation steps, containment guidance, and mitigations.465. Preserve uncertainty: distinguish confirmed evidence, plausible indicators, assumptions, and gaps. Recommend what to collect next.476. 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.4849## Bundled resources5051- `references/technique-profile.json`: machine-readable ATT&CK metadata for this technique.52- `references/detection-and-mitigation.md`: detection notes, telemetry checklist, triage questions, mitigation candidates, and false-positive considerations.53- `references/known-threat-context.md`: ATT&CK relationship context with attribution cautions.54- `templates/detection-brief.md`: detection engineering brief template.55- `templates/hunt-plan.md`: threat hunt plan template.56- `templates/incident-response-note.md`: incident response note template.57- `templates/coverage-assessment.md`: ATT&CK coverage assessment template.58- `scripts/render_brief.py`: local helper that renders a Markdown defensive brief from `technique-profile.json`.59- `assets/output-schema.json`: JSON schema for structured technique analysis outputs.6061To generate a quick brief, run `python scripts/render_brief.py --output brief.md` from inside this skill directory, or adapt the templates directly.6263## Detection guidance6465No ATT&CK detection guidance was present in the source STIX object.6667## Useful telemetry and data sources6869- Not specified in the STIX object.7071## Mitigations to consider7273- User Guidance7475## Known threat context7677Use these examples only as contextual leads, not as proof that an observed event is this technique:7879- APT-C-23 (intrusion-set)80- Agent Smith (malware)81- AndroRAT (malware)82- Android/AdDisplay.Ashas (malware)83- Android/SpyAgent (malware)84- AndroidOS/MalLocker.B (malware)85- Anubis (malware)86- Asacub (malware)87- BOULDSPY (malware)88- BRATA (malware)89- Bouncing Golf (intrusion-set)90- C0033 (campaign)91- CHEMISTGAMES (malware)92- CarbonSteal (malware)93- Cerberus (malware)94- Chameleon (malware)95- DCHSpy (malware)96- Dendroid (malware)97- DocSwap (malware)98- DoubleAgent (malware)99100## Recommended output pattern101102When responding with this skill, structure the answer as:103104- Assessment: whether the evidence supports this ATT&CK mapping and why.105- Evidence: specific indicators, logs, behaviors, and assumptions.106- Detection: telemetry sources, analytic logic, and tuning considerations.107- Response: containment, eradication, recovery, and validation actions.108- Coverage gaps: missing logs, sensors, controls, or environmental details.109- References: include the ATT&CK URL and any user-provided evidence references.110111## ATT&CK contributors112113- Ford Qin, Trend Micro114- Liran Ravich, CardinalOps