MITRE ATT&CK T1516: Input Injection
When to use this skill
Use this skill when the task involves T1516, Input Injection, 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: T1516
- Technique name: Input Injection
- Type: technique
- ATT&CK URL: https://attack.mitre.org/techniques/T1516
- Tactics: defense-evasion, impact
- Platforms: Android
- Required permissions: Not specified
- Effective permissions: Not specified
- Defenses bypassed: Not specified
ATT&CK description
A malicious application can inject input to the user interface to mimic user interaction through the abuse of Android's accessibility APIs.
Input Injection can be achieved using any of the following methods:
- Mimicking user clicks on the screen, for example to steal money from a user's PayPal account.(Citation: android-trojan-steals-paypal-2fa)
- Injecting global actions, such as
GLOBAL_ACTION_BACK (programatically mimicking a physical back button press), to trigger actions on behalf of the user.(Citation: Talos Gustuff Apr 2019)
- Inserting input into text fields on behalf of the user. This method is used legitimately to auto-fill text fields by applications such as password managers.(Citation: bitwarden autofill logins)
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
- Enterprise Policy
- User Guidance
Known threat context
Use these examples only as contextual leads, not as proof that an observed event is this technique:
- BRATA (malware)
- Cerberus (malware)
- Crocodilus (malware)
- DEFENSOR ID (malware)
- Ginp (malware)
- GodFather (malware)
- Gustuff (malware)
- Mandrake (malware)
- Riltok (malware)
- S.O.V.A. (malware)
- SharkBot (malware)
- TERRACOTTA (malware)
- TrickMo (malware)
- Zen (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
1---2name: attack-mob-t1516-input-injection3description: "Analyze MITRE ATT&CK T1516 Input Injection in the mobile matrix. Use for TTP triage, detection engineering, hunting, defensive emulation planning, mitigations, incident response mapping, ATT&CK coverage, or questions mentioning T1516, Input Injection, or mobile ATT&CK. A malicious application can inject input to the user interface to mimic user interaction through the abuse of Android's accessibility APIs."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-t1516-input-injection7 upstream: mitre-attack/attack-stix-data8 domain: mobile9 attack_id: T151610 attack_stix_id: attack-pattern--d1f1337e-aea7-454c-86bd-482a98ffaf6211 attack_version: "1.2"12 attack_modified: "2025-10-24T17:49:25.635Z"13---1415# MITRE ATT&CK T1516: Input Injection1617## When to use this skill1819Use this skill when the task involves T1516, Input Injection, 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: T151625- Technique name: Input Injection26- Type: technique27- ATT&CK URL: https://attack.mitre.org/techniques/T151628- Tactics: defense-evasion, impact29- Platforms: Android30- Required permissions: Not specified31- Effective permissions: Not specified32- Defenses bypassed: Not specified3334## ATT&CK description3536A malicious application can inject input to the user interface to mimic user interaction through the abuse of Android's accessibility APIs.3738[Input Injection](https://attack.mitre.org/techniques/T1516) can be achieved using any of the following methods:3940* Mimicking user clicks on the screen, for example to steal money from a user's PayPal account.(Citation: android-trojan-steals-paypal-2fa)41* Injecting global actions, such as `GLOBAL_ACTION_BACK` (programatically mimicking a physical back button press), to trigger actions on behalf of the user.(Citation: Talos Gustuff Apr 2019)42* Inserting input into text fields on behalf of the user. This method is used legitimately to auto-fill text fields by applications such as password managers.(Citation: bitwarden autofill logins)4344## Agent workflow45461. 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.472. 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.483. 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.494. Produce defensive outputs: prioritize hypotheses, telemetry requirements, detection logic ideas, validation steps, containment guidance, and mitigations.505. Preserve uncertainty: distinguish confirmed evidence, plausible indicators, assumptions, and gaps. Recommend what to collect next.516. 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.5253## Bundled resources5455- `references/technique-profile.json`: machine-readable ATT&CK metadata for this technique.56- `references/detection-and-mitigation.md`: detection notes, telemetry checklist, triage questions, mitigation candidates, and false-positive considerations.57- `references/known-threat-context.md`: ATT&CK relationship context with attribution cautions.58- `templates/detection-brief.md`: detection engineering brief template.59- `templates/hunt-plan.md`: threat hunt plan template.60- `templates/incident-response-note.md`: incident response note template.61- `templates/coverage-assessment.md`: ATT&CK coverage assessment template.62- `scripts/render_brief.py`: local helper that renders a Markdown defensive brief from `technique-profile.json`.63- `assets/output-schema.json`: JSON schema for structured technique analysis outputs.6465To generate a quick brief, run `python scripts/render_brief.py --output brief.md` from inside this skill directory, or adapt the templates directly.6667## Detection guidance6869No ATT&CK detection guidance was present in the source STIX object.7071## Useful telemetry and data sources7273- Not specified in the STIX object.7475## Mitigations to consider7677- Enterprise Policy78- User Guidance7980## Known threat context8182Use these examples only as contextual leads, not as proof that an observed event is this technique:8384- BRATA (malware)85- Cerberus (malware)86- Crocodilus (malware)87- DEFENSOR ID (malware)88- Ginp (malware)89- GodFather (malware)90- Gustuff (malware)91- Mandrake (malware)92- Riltok (malware)93- S.O.V.A. (malware)94- SharkBot (malware)95- TERRACOTTA (malware)96- TrickMo (malware)97- Zen (malware)9899## Recommended output pattern100101When responding with this skill, structure the answer as:102103- Assessment: whether the evidence supports this ATT&CK mapping and why.104- Evidence: specific indicators, logs, behaviors, and assumptions.105- Detection: telemetry sources, analytic logic, and tuning considerations.106- Response: containment, eradication, recovery, and validation actions.107- Coverage gaps: missing logs, sensors, controls, or environmental details.108- References: include the ATT&CK URL and any user-provided evidence references.109110## ATT&CK contributors111112- Lukáš Štefanko, ESET