# Attack Mob T1638 Adversary In The Middle > Analyze MITRE ATT&CK T1638 Adversary-in-the-Middle in the mobile matrix. Use for TTP triage, detection engineering, hunting, defensive emulation planning, mitigations, incident response mapping, ATT&CK coverage, or questions mentioning T1638, Adversary-in-the-Middle, or mobile ATT&CK. Adversaries may attempt to position themselves between two or more networked devices to support follow-on behaviors such as [Transmitted Data Manipulation](https://attack.mitre.org/techniques/T1565/002) or [Endpoint Den… - Skill: `santosomar/attack-mob-t1638-adversary-in-the-middle` (Agent Skill, multi-file: 11 files) - Install (CLI): `npx skillmds@latest add santosomar/attack-mob-t1638-adversary-in-the-middle` - Raw SKILL.md: https://api.skillmd.com/api/skills/santosomar/attack-mob-t1638-adversary-in-the-middle/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-t1638-adversary-in-the-middle --- # MITRE ATT&CK T1638: Adversary-in-the-Middle ## When to use this skill Use this skill when the task involves T1638, Adversary-in-the-Middle, 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: T1638 - Technique name: Adversary-in-the-Middle - Type: technique - ATT&CK URL: https://attack.mitre.org/techniques/T1638 - Tactics: collection - Platforms: Android, iOS - Required permissions: Not specified - Effective permissions: Not specified - Defenses bypassed: Not specified ## ATT&CK description Adversaries may attempt to position themselves between two or more networked devices to support follow-on behaviors such as [Transmitted Data Manipulation](https://attack.mitre.org/techniques/T1565/002) or [Endpoint Denial of Service](https://attack.mitre.org/techniques/T1642). [Adversary-in-the-Middle](https://attack.mitre.org/techniques/T1638) can be achieved through several mechanisms. For example, a malicious application may register itself as a VPN client, effectively redirecting device traffic to adversary-owned resources. Registering as a VPN client requires user consent on both Android and iOS; additionally, a special entitlement granted by Apple is needed for iOS devices. Alternatively, a malicious application with escalation privileges may utilize those privileges to gain access to network traffic. Specific to Android devices, adversary-in-the-disk is a type of AiTM attack where adversaries monitor and manipulate data that is exchanged between applications and external storage.(Citation: mitd_kaspersky)(Citation: mitd_checkpoint)(Citation: mitd_checkpoint_research) To accomplish this, a malicious application firsts requests for access to multimedia files on the device (`READ_EXTERNAL STORAGE` and `WRITE_EXTERNAL_STORAGE`), then the application reads data on the device and/or writes malware to the device. Though the request for access is common, when used maliciously, adversaries may access files and other sensitive data due to abusing the permission. Multiple applications were shown to be vulnerable against this attack; however, scrutiny of permissions and input validations may mitigate this attack. Outside of a mobile device, adversaries may be able to capture traffic by employing a rogue base station or Wi-Fi access point. These devices will allow adversaries to capture network traffic after it has left the device, while it is flowing to its destination. On a local network, enterprise techniques could be used, such as [ARP Cache Poisoning](https://attack.mitre.org/techniques/T1557/002) or [DHCP Spoofing](https://attack.mitre.org/techniques/T1557/003). If applications properly encrypt their network traffic, sensitive data may not be accessible to adversaries, depending on the point of capture. For example, properly implementing Apple’s Application Transport Security (ATS) and Android’s Network Security Configuration (NSC) may prevent sensitive data leaks.(Citation: NSC_Android) ## 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 - Encrypt Network Traffic - Use Recent OS Version ## Known threat context Use these examples only as contextual leads, not as proof that an observed event is this technique: - KeyRaider (malware) - Monokle (malware) - S.O.V.A. (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.