FairPlay DRM Triage & iOS Decryption Guide
Binaries downloaded directly from the Apple App Store are protected by FairPlay DRM encryption. The executable __TEXT code section is encrypted on disk and only decrypted into RAM at launch by the kernel. Static decompilers cannot read encrypted machine instructions without prior decryption.
Phase 0: Detecting FairPlay Encryption
Always inspect the encryption load command before spending time running static teardown or Ghidra decompilation.
To check encryption status of an IPA, app bundle, or Mach-O file:
bash scripts/check-encryption.sh app.ipa
The script parses LC_ENCRYPTION_INFO (32-bit, 0x21) and LC_ENCRYPTION_INFO_64 (64-bit, 0x2C):
cryptid == 0: The binary is unencrypted / plaintext. Proceed directly to static analysis, Ghidra decompilation, and API extraction.cryptid == 1: The binary is FairPlay encrypted. Static analysis will show encrypted pseudorandom bytes in__text. The app must be decrypted on a device before analysis.
To inspect embedded frameworks and app extensions recursively:
bash scripts/check-encryption.sh --recursive app.ipa
Decryption Workflows on iOS Devices
Because the FairPlay decryption keys are held by Apple Silicon hardware and the kernel, decryption is accomplished by launching the application on a jailbroken or debug-enabled device and dumping the unencrypted memory pages.
Workflow A: Modern Device Dumping with bagbak
The modern standard for on-device IPA dumping using Frida:
pip install bagbak
bagbak com.example.app
bagbak spawns the app on the USB-connected device, pauses execution immediately after the kernel decrypts the __TEXT segment, dumps memory to disk, sets cryptid to 0, and repacks an unencrypted IPA.
Workflow B: frida-ios-dump
Classic Frida dumping script:
iproxy 2222 22 &
python3 dump.py com.example.app -o DecryptedApp.ipa