MITRE ATT&CK T1544: Ingress Tool Transfer
When to use this skill
Use this skill when the task involves T1544, Ingress Tool Transfer, 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: T1544
- Technique name: Ingress Tool Transfer
- Type: technique
- ATT&CK URL: https://attack.mitre.org/techniques/T1544
- Tactics: command-and-control
- Platforms: Android, iOS
- Required permissions: Not specified
- Effective permissions: Not specified
- Defenses bypassed: Not specified
ATT&CK description
Adversaries may transfer tools or other files from an external system onto a compromised device to facilitate follow-on actions. Files may be copied from an external adversary-controlled system through the command and control channel or through alternate protocols with another tool such as FTP.
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
- No ATT&CK mitigation relationships were present in the source STIX bundle.
Known threat context
Use these examples only as contextual leads, not as proof that an observed event is this technique:
- AbstractEmu (malware)
- C0033 (campaign)
- Chameleon (malware)
- CherryBlos (malware)
- DocSwap (malware)
- GodFather (malware)
- LightSpy (malware)
- Mandrake (malware)
- Monokle (malware)
- Operation Triangulation (campaign)
- Phenakite (malware)
- RedDrop (malware)
- SharkBot (malware)
- SpyC23 (malware)
- Sunbird (malware)
- TriangleDB (malware)
- ViceLeaker (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.
1---2name: attack-mob-t1544-ingress-tool-transfer3description: "Analyze MITRE ATT&CK T1544 Ingress Tool Transfer in the mobile matrix. Use for TTP triage, detection engineering, hunting, defensive emulation planning, mitigations, incident response mapping, ATT&CK coverage, or questions mentioning T1544, Ingress Tool Transfer, or mobile ATT&CK. Adversaries may transfer tools or other files from an external system onto a compromised device to facilitate follow-on actions."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-t1544-ingress-tool-transfer7 upstream: mitre-attack/attack-stix-data8 domain: mobile9 attack_id: T154410 attack_stix_id: attack-pattern--2bb20118-e6c0-41dc-a07c-283ea4dd0fb811 attack_version: "2.2"12 attack_modified: "2025-10-24T17:48:34.355Z"13---1415# MITRE ATT&CK T1544: Ingress Tool Transfer1617## When to use this skill1819Use this skill when the task involves T1544, Ingress Tool Transfer, 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: T154425- Technique name: Ingress Tool Transfer26- Type: technique27- ATT&CK URL: https://attack.mitre.org/techniques/T154428- Tactics: command-and-control29- Platforms: Android, iOS30- Required permissions: Not specified31- Effective permissions: Not specified32- Defenses bypassed: Not specified3334## ATT&CK description3536Adversaries may transfer tools or other files from an external system onto a compromised device to facilitate follow-on actions. Files may be copied from an external adversary-controlled system through the command and control channel or through alternate protocols with another tool such as FTP.3738## Agent workflow39401. 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.412. 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.423. 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.434. Produce defensive outputs: prioritize hypotheses, telemetry requirements, detection logic ideas, validation steps, containment guidance, and mitigations.445. Preserve uncertainty: distinguish confirmed evidence, plausible indicators, assumptions, and gaps. Recommend what to collect next.456. 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.4647## Bundled resources4849- `references/technique-profile.json`: machine-readable ATT&CK metadata for this technique.50- `references/detection-and-mitigation.md`: detection notes, telemetry checklist, triage questions, mitigation candidates, and false-positive considerations.51- `references/known-threat-context.md`: ATT&CK relationship context with attribution cautions.52- `templates/detection-brief.md`: detection engineering brief template.53- `templates/hunt-plan.md`: threat hunt plan template.54- `templates/incident-response-note.md`: incident response note template.55- `templates/coverage-assessment.md`: ATT&CK coverage assessment template.56- `scripts/render_brief.py`: local helper that renders a Markdown defensive brief from `technique-profile.json`.57- `assets/output-schema.json`: JSON schema for structured technique analysis outputs.5859To generate a quick brief, run `python scripts/render_brief.py --output brief.md` from inside this skill directory, or adapt the templates directly.6061## Detection guidance6263No ATT&CK detection guidance was present in the source STIX object.6465## Useful telemetry and data sources6667- Not specified in the STIX object.6869## Mitigations to consider7071- No ATT&CK mitigation relationships were present in the source STIX bundle.7273## Known threat context7475Use these examples only as contextual leads, not as proof that an observed event is this technique:7677- AbstractEmu (malware)78- C0033 (campaign)79- Chameleon (malware)80- CherryBlos (malware)81- DocSwap (malware)82- GodFather (malware)83- LightSpy (malware)84- Mandrake (malware)85- Monokle (malware)86- Operation Triangulation (campaign)87- Phenakite (malware)88- RedDrop (malware)89- SharkBot (malware)90- SpyC23 (malware)91- Sunbird (malware)92- TriangleDB (malware)93- ViceLeaker (malware)9495## Recommended output pattern9697When responding with this skill, structure the answer as:9899- Assessment: whether the evidence supports this ATT&CK mapping and why.100- Evidence: specific indicators, logs, behaviors, and assumptions.101- Detection: telemetry sources, analytic logic, and tuning considerations.102- Response: containment, eradication, recovery, and validation actions.103- Coverage gaps: missing logs, sensors, controls, or environmental details.104- References: include the ATT&CK URL and any user-provided evidence references.