# Attack Mob T1644 Out Of Band Data > Analyze MITRE ATT&CK T1644 Out of Band Data in the mobile matrix. Use for TTP triage, detection engineering, hunting, defensive emulation planning, mitigations, incident response mapping, ATT&CK coverage, or questions mentioning T1644, Out of Band Data, or mobile ATT&CK. Adversaries may communicate with compromised devices using out of band data streams. - Skill: `santosomar/attack-mob-t1644-out-of-band-data` (Agent Skill, multi-file: 11 files) - Install (CLI): `npx skillmds@latest add santosomar/attack-mob-t1644-out-of-band-data` - Raw SKILL.md: https://api.skillmd.com/api/skills/santosomar/attack-mob-t1644-out-of-band-data/raw - Safety review: pending - Works with: Claude Code, Claude.ai, OpenAI Codex - Category: Coding & Dev Tools - License: MITRE ATT&CK Terms of Use apply to ATT&CK-derived content. See h - Author: santosomar (https://skillmd.com/u/santosomar) - Updated: 2026-09-22 - Page: https://skillmd.com/skills/santosomar/attack-mob-t1644-out-of-band-data --- # MITRE ATT&CK T1644: Out of Band Data ## When to use this skill Use this skill when the task involves T1644, Out of Band Data, 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: T1644 - Technique name: Out of Band Data - Type: technique - ATT&CK URL: https://attack.mitre.org/techniques/T1644 - Tactics: command-and-control - Platforms: Android, iOS - Required permissions: Not specified - Effective permissions: Not specified - Defenses bypassed: Not specified ## ATT&CK description Adversaries may communicate with compromised devices using out of band data streams. This could be done for a variety of reasons, including evading network traffic monitoring, as a backup method of command and control, or for data exfiltration if the device is not connected to any Internet-providing networks (i.e. cellular or Wi-Fi). Several out of band data streams exist, such as SMS messages, NFC, and Bluetooth. On Android, applications can read push notifications to capture content from SMS messages, or other out of band data streams. This requires that the user manually grant notification access to the application via the settings menu. However, the application could launch an Intent to take the user directly there. On iOS, there is no way to programmatically read push notifications. ## Agent workflow 1. 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. 2. 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. 3. 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. 4. Produce defensive outputs: prioritize hypotheses, telemetry requirements, detection logic ideas, validation steps, containment guidance, and mitigations. 5. Preserve uncertainty: distinguish confirmed evidence, plausible indicators, assumptions, and gaps. Recommend what to collect next. 6. 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 - User Guidance ## Known threat context Use these examples only as contextual leads, not as proof that an observed event is this technique: - Android/Chuli.A (malware) - BOULDSPY (malware) - BusyGasper (malware) - CarbonSteal (malware) - Desert Scorpion (malware) - Gustuff (malware) - Monokle (malware) - Pegasus for Android (malware) - Pegasus for iOS (malware) - RCSAndroid (malware) - Rotexy (malware) - SharkBot (malware) - Skygofree (malware) - SpyC23 (malware) - SpyDealer (malware) - Stealth Mango (malware) - TriangleDB (malware) - TrickMo (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.