Evil maid → sniff TPM unseal → decrypt BitLocker offline
Brief physical access to a TPM-only BitLocker laptop. Plug a logic analyser onto the LPC / SPI bus; capture the FVEK as the TPM unseals it at boot. Take the disk home, decrypt offline.
§ Context
Assumed environment: target laptop uses BitLocker with TPM-only protector (no PIN). Chassis can be opened in minutes; SPI / LPC bus accessible. Demonstrated repeatedly with ~10 USD logic analyzers.
§ Steps
- 01Exfil clear-text dataExfiltrationT1041— Exfiltration Over C2 Channel
- 02Decrypt offline with captured keyCredential AccessT1552— Unsecured Credentials
- 03Image the encrypted diskDiscoveryT1083— File and Directory Discovery
- 04Attach logic analyzer to TPM busInitial AccessIOT-UART-CONSOLE— UART Debug Console
- 05Open laptop chassisInitial AccessFW-EVIL-MAID— Evil Maid Boot Tamper
- 06Trigger boot, capture FVEK on the wireCredential AccessFW-TPM-RELAY— TPM Sniffing / Relay (BitLocker)
§ References
§ Frequently asked
- What is the "Evil maid → sniff TPM unseal → decrypt BitLocker offline" attack path?
- Brief physical access to a TPM-only BitLocker laptop. Plug a logic analyser onto the LPC / SPI bus; capture the FVEK as the TPM unseals it at boot. Take the disk home, decrypt offline. It chains 6 steps drawn from real-world offensive-security techniques.
- What starting position does this attack require?
- The first step is Exfil clear-text data (T1041) — a exfiltration primitive. Assumed environment: target laptop uses BitLocker with TPM-only protector (no PIN).
- What is the final impact of this kill-chain?
- The final step lands on Trigger boot, capture FVEK on the wire (FW-TPM-RELAY), which falls under Credential Access. From here, an operator typically pivots into post-exploitation or maintains persistence.
- How can defenders detect or prevent this attack?
- Detection and prevention vary per step. Refer to each linked MITRE ATT&CK entry under "References" — every technique on that page lists defensive controls, detection telemetry, and known threat-actor usage.
§ Related dossiers
- Shared techniques3
Exported ContentProvider → private data leak
App exports a ContentProvider for legitimate inter-app integration but forgets to enforce grantUri / signature permissions — a rogue installed app reads private auth tokens.
- Shared techniques2
Apache Struts S2-045 (CVE-2017-5638) → Equifax-style breach
Crafted Content-Type header is parsed as OGNL — execute commands as the app user. The 2017 Equifax breach origin: unpatched Struts endpoint exposed to the internet.
- Shared techniques2
User foothold → keychain dump → cloud creds
Standard user shell on macOS. Brute the login.keychain master via ChainBreaker / a keylogged password; dump all entries — Safari saved creds, AWS keys, Slack tokens, SSO cookies.