MITRE ATT&CK T1417.001: Keylogging
When to use this skill
Use this skill when the task involves T1417.001, Keylogging, 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: T1417.001
- Technique name: Keylogging
- Type: sub-technique
- ATT&CK URL: https://attack.mitre.org/techniques/T1417/001
- Tactics: collection, credential-access
- Platforms: Android, iOS
- Required permissions: Not specified
- Effective permissions: Not specified
- Defenses bypassed: Not specified
ATT&CK description
Adversaries may log user keystrokes to intercept credentials or other information from the user as the user types them.
Some methods of keylogging include:
- Masquerading as a legitimate third-party keyboard to record user keystrokes.(Citation: Zeltser-Keyboard) On both Android and iOS, users must explicitly authorize the use of third-party keyboard apps. Users should be advised to use extreme caution before granting this authorization when it is requested.
- Abusing accessibility features. On Android, adversaries may abuse accessibility features to record keystrokes by registering an
AccessibilityService class, overriding the onAccessibilityEvent method, and listening for the AccessibilityEvent.TYPE_VIEW_TEXT_CHANGED event type. The event object passed into the function will contain the data that the user typed.
*Additional methods of keylogging may be possible if root access is available.
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:
- Anubis (malware)
- BOULDSPY (malware)
- BRATA (malware)
- BusyGasper (malware)
- Cerberus (malware)
- Chameleon (malware)
- Crocodilus (malware)
- DocSwap (malware)
- Drinik (malware)
- Escobar (malware)
- EventBot (malware)
- Exobot (malware)
- FlexiSpy (tool)
- GodFather (malware)
- Gustuff (malware)
- Monokle (malware)
- S.O.V.A. (malware)
- SharkBot (malware)
- VajraSpy (malware)
- Windshift (intrusion-set)
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-t1417-001-keylogging3description: "Analyze MITRE ATT&CK T1417.001 Keylogging in the mobile matrix. Use for TTP triage, detection engineering, hunting, defensive emulation planning, mitigations, incident response mapping, ATT&CK coverage, or questions mentioning T1417.001, Keylogging, or mobile ATT&CK. Adversaries may log user keystrokes to intercept credentials or other information from the user as the user types 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-t1417-001-keylogging7 upstream: mitre-attack/attack-stix-data8 domain: mobile9 attack_id: T1417.00110 attack_stix_id: attack-pattern--b1c95426-2550-4621-8028-ceebf28b3a4711 attack_version: "1.1"12 attack_modified: "2025-10-24T17:49:14.276Z"13---1415# MITRE ATT&CK T1417.001: Keylogging1617## When to use this skill1819Use this skill when the task involves T1417.001, Keylogging, 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: T1417.00125- Technique name: Keylogging26- Type: sub-technique27- ATT&CK URL: https://attack.mitre.org/techniques/T1417/00128- Tactics: collection, credential-access29- Platforms: Android, iOS30- Required permissions: Not specified31- Effective permissions: Not specified32- Defenses bypassed: Not specified3334## ATT&CK description3536Adversaries may log user keystrokes to intercept credentials or other information from the user as the user types them.3738Some methods of keylogging include:3940* Masquerading as a legitimate third-party keyboard to record user keystrokes.(Citation: Zeltser-Keyboard) On both Android and iOS, users must explicitly authorize the use of third-party keyboard apps. Users should be advised to use extreme caution before granting this authorization when it is requested.41* Abusing accessibility features. On Android, adversaries may abuse accessibility features to record keystrokes by registering an `AccessibilityService` class, overriding the `onAccessibilityEvent` method, and listening for the `AccessibilityEvent.TYPE_VIEW_TEXT_CHANGED` event type. The event object passed into the function will contain the data that the user typed. 42*Additional methods of keylogging may be possible if root access is available.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- Anubis (malware)85- BOULDSPY (malware)86- BRATA (malware)87- BusyGasper (malware)88- Cerberus (malware)89- Chameleon (malware)90- Crocodilus (malware)91- DocSwap (malware)92- Drinik (malware)93- Escobar (malware)94- EventBot (malware)95- Exobot (malware)96- FlexiSpy (tool)97- GodFather (malware)98- Gustuff (malware)99- Monokle (malware)100- S.O.V.A. (malware)101- SharkBot (malware)102- VajraSpy (malware)103- Windshift (intrusion-set)104105## Recommended output pattern106107When responding with this skill, structure the answer as:108109- Assessment: whether the evidence supports this ATT&CK mapping and why.110- Evidence: specific indicators, logs, behaviors, and assumptions.111- Detection: telemetry sources, analytic logic, and tuning considerations.112- Response: containment, eradication, recovery, and validation actions.113- Coverage gaps: missing logs, sensors, controls, or environmental details.114- References: include the ATT&CK URL and any user-provided evidence references.