MITRE ATT&CK T1533: Data from Local System
When to use this skill
Use this skill when the task involves T1533, Data from Local System, 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: T1533
- Technique name: Data from Local System
- Type: technique
- ATT&CK URL: https://attack.mitre.org/techniques/T1533
- Tactics: collection
- Platforms: Android, iOS
- Required permissions: Not specified
- Effective permissions: Not specified
- Defenses bypassed: Not specified
ATT&CK description
Adversaries may search local system sources, such as file systems or local databases, to find files of interest and sensitive data prior to exfiltration.
Access to local system data, which includes information stored by the operating system, often requires escalated privileges. Examples of local system data include authentication tokens, the device keyboard cache, Wi-Fi passwords, and photos. On Android, adversaries may also attempt to access files from external storage which may require additional storage-related permissions.
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)
- AhRat (malware)
- Anubis (malware)
- BOULDSPY (malware)
- BRATA (malware)
- Binary Validator (malware)
- BusyGasper (malware)
- CHEMISTGAMES (malware)
- Chameleon (malware)
- Concipit1248 (malware)
- Corona Updates (malware)
- DCHSpy (malware)
- Dendroid (malware)
- Desert Scorpion (malware)
- DocSwap (malware)
- DoubleAgent (malware)
- Drinik (malware)
- Escobar (malware)
- Exodus (malware)
- Fakecalls (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-t1533-data-from-local-system3description: "Analyze MITRE ATT&CK T1533 Data from Local System in the mobile matrix. Use for TTP triage, detection engineering, hunting, defensive emulation planning, mitigations, incident response mapping, ATT&CK coverage, or questions mentioning T1533, Data from Local System, or mobile ATT&CK. Adversaries may search local system sources, such as file systems or local databases, to find files of interest and sensitive data prior to exfiltration."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-t1533-data-from-local-system7 upstream: mitre-attack/attack-stix-data8 domain: mobile9 attack_id: T153310 attack_stix_id: attack-pattern--e1c912a9-e305-434b-9172-8a6ce3ec9c4a11 attack_version: "1.1"12 attack_modified: "2025-10-24T17:49:30.706Z"13---1415# MITRE ATT&CK T1533: Data from Local System1617## When to use this skill1819Use this skill when the task involves T1533, Data from Local System, 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: T153325- Technique name: Data from Local System26- Type: technique27- ATT&CK URL: https://attack.mitre.org/techniques/T153328- Tactics: collection29- Platforms: Android, iOS30- Required permissions: Not specified31- Effective permissions: Not specified32- Defenses bypassed: Not specified3334## ATT&CK description3536Adversaries may search local system sources, such as file systems or local databases, to find files of interest and sensitive data prior to exfiltration. 3738 3940Access to local system data, which includes information stored by the operating system, often requires escalated privileges. Examples of local system data include authentication tokens, the device keyboard cache, Wi-Fi passwords, and photos. On Android, adversaries may also attempt to access files from external storage which may require additional storage-related permissions.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- No ATT&CK mitigation relationships were present in the source STIX bundle.7677## Known threat context7879Use these examples only as contextual leads, not as proof that an observed event is this technique:8081- AbstractEmu (malware)82- AhRat (malware)83- Anubis (malware)84- BOULDSPY (malware)85- BRATA (malware)86- Binary Validator (malware)87- BusyGasper (malware)88- CHEMISTGAMES (malware)89- Chameleon (malware)90- Concipit1248 (malware)91- Corona Updates (malware)92- DCHSpy (malware)93- Dendroid (malware)94- Desert Scorpion (malware)95- DocSwap (malware)96- DoubleAgent (malware)97- Drinik (malware)98- Escobar (malware)99- Exodus (malware)100- Fakecalls (malware)101102## Recommended output pattern103104When responding with this skill, structure the answer as:105106- Assessment: whether the evidence supports this ATT&CK mapping and why.107- Evidence: specific indicators, logs, behaviors, and assumptions.108- Detection: telemetry sources, analytic logic, and tuning considerations.109- Response: containment, eradication, recovery, and validation actions.110- Coverage gaps: missing logs, sensors, controls, or environmental details.111- References: include the ATT&CK URL and any user-provided evidence references.