← RegistryDossier · 5 steps · 4 edges
Jailbreak detection bypass → keychain dump
Test on a jailbroken device. Hook jailbreak-detection routines, run objection to dump the entire app keychain — recovers session tokens, refresh tokens, biometric keys.
Filed by AD Knowledge Base
§ Kill-chainDrag · zoom · scroll
§ Context
Assumed environment: jailbroken iOS device (palera1n / Dopamine) with Frida-server installed. Target IPA can be installed via TrollStore / sideloadly.
§ Steps
- 01Replay tokens against the APIInitial AccessT1078— Valid Accounts
- 02ios keychain dumpCredential AccessMOB-IOS-KEYCHAIN— iOS Keychain Dump (jailbroken)
- 03Bypass jailbreak detection (Liberty / Frida)Defense EvasionMOB-IOS-JB-BYPASS— iOS Jailbreak Detection Bypass
- 04Sideload IPA on jailbroken deviceDefense EvasionMOB-IOS-IPA-RESIGN— IPA Repackaging / Resigning
- 05objection -g <pkg> exploreExecutionMOB-FRIDA-HOOK— Frida Runtime Hooking
§ References
- T1078Valid Accounts
§ Frequently asked
- What is the "Jailbreak detection bypass → keychain dump" attack path?
- Test on a jailbroken device. Hook jailbreak-detection routines, run objection to dump the entire app keychain — recovers session tokens, refresh tokens, biometric keys. It chains 5 steps drawn from real-world offensive-security techniques.
- What starting position does this attack require?
- The first step is Replay tokens against the API (T1078) — a initial access primitive. Assumed environment: jailbroken iOS device (palera1n / Dopamine) with Frida-server installed.
- What is the final impact of this kill-chain?
- The final step lands on objection -g <pkg> explore (MOB-FRIDA-HOOK), which falls under Execution. 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.