Skip to content
KitploitKITPLOIT
ToolsExploitsBlog
Log in
Submit
ToolsExploitsBlog
Submit

Hacking, PenTest, and Cybersecurity Tools for Your Security Arsenal!

Kitploit is a directory of hacking, cybersecurity, and pentesting tools. Discover the latest project updates to find vulnerabilities, analyze systems, automate testing, and strengthen your security.

FeedsContactPrivacy© 2026 Kitploit

Tool Directory

Categories

View all categories
Loading categories
ABrake27 — iOS 27 kernelcache RE: SEP dispatch map, AMFI diff, Ghidra workflow. | Kitploit
Tools/GitHubGitHub/vvirei333/abrake27
iOS SecurityVulnerability AnalysisExploitationMobile App PentestingReverse EngineeringMobile SecurityBinary AnalysisPapers & ResearchLearning & EducationPayload DevelopmentFirmware Analysis
1041099 days agoNot yet reviewed
Share
GitHub
vvirei333/abrake27

ABrake27

iOS 27 kernelcache RE: SEP dispatch map, AMFI diff, Ghidra workflow.

View Repository

ABrake27

iOS 27 kernelcache reverse engineering — firmware diffing, AMFI/SEP RE, and Linux-native tooling (arm64/arm64e)

Platform Method Arch Status

Research-grade, documentation-first project. Binary diff of iOS 27.0.1 (24A446) vs 27.2 beta (24B5089g) on iPhone14,5, reverse-engineering the AMFI and AppleSEPUserClient IOUserClient dispatch surfaces, and a fully verified, reproducible Developer Mode enablement path through Apple's stock lockdown protocol — all done from Linux, no Mac, no Xcode.

Flagship open lead: silent ASTC/DDS hardening in ImageIO with the delivery chain mapped — iMessage attachment → BlastDoor → IAKC container (first public documentation of the format) → mediaanalysisd → ASTC parser. See STATUS.md and research/intel/ma_decomp/VERDICT.md.

Status

Project paused. The research device (iPhone 13) has been sold; all remaining work is static (firmware/binary analysis), which the repo tooling fully supports. The authoritative state summary lives in STATUS.md; the complete session-by-session journal in HANDOFF.md (31 sessions).

What was achieved while active:

  • 31 documented sessions across firmware diff, kernelcache RE, and userland diff
  • 4 research threads fully closed (2 as negative findings, 2 as documentation)
  • 1 reproducible verified result (Developer Mode protocol)
  • 2 open leads: ImageIO ASTC/DDS hardening (flagship), rlebuf format-string

What This Repo Contains

1. Firmware diff (iOS 27.0.1 vs 27.2 beta, iPhone14,5)

Kernelcache (MH_FILESET, arm64e), kexts, sandbox profiles, entitlements — full reports in diff_output/. Methodology: normalized structural diffing with difflib.SequenceMatcher to separate logic changes from relocation noise, plus a "vtable + registry membership" reachability shortcut.

2. AMFI / SEP reverse engineering

  • AppleMobileFileIntegrityUserClient — 18 selectors decoded (both builds); selector 11 = armSecurityBootMode; dev-mode flag analysis (AMFI only reads the flag — ACM is the source of truth via command 0x25)
  • AppleSEPUserClient — full dispatch surface decoded: 19 IOExternalMethodDispatch2022 tables, 124 selectors, chained-fixup format (ARM64E) documented in HANDOFF.md
  • Whitepaper: docs/WHITEPAPER.md

3. Developer Mode via stock lockdown protocol (verified, reproducible)

The iOS Developer Mode chain can be driven entirely through com.apple.amfi.lockdown with pymobiledevice3 on Linux — no jailbreak, no IPA, no entitlement forging. Verified persistent at kernel level (mounter query-developer-mode-status → true, DDI mounted at /System/Developer) across an independent reboot. Full protocol and honesty log: FINDINGS_LOCK.md.

Prerequisite: remove the passcode (Settings → Face ID & Passcode → Turn Off Passcode).

# 1) enable → action=1 → REBOOT #1
python3 -m pymobiledevice3 amfi enable-developer-mode

# 2) after boot: post-restart accept → action=2 → REBOOT #2
#    (CLI has no separate accept command — use poc/verify_now2.py)

# 3) reveal the Settings toggle → action=0
python3 -m pymobiledevice3 amfi reveal-developer-mode

# Verify (kernel-level, independent of the AMFI service):
python3 -m pymobiledevice3 mounter query-developer-mode-status   # → true
python3 -m pymobiledevice3 mounter list                          # IsMounted: true
actionMeaningEffect
0revealShows the Developer Mode toggle in Settings
1enableSets the flag, reboots the device
2acceptPost-restart confirmation, reboots again

⚠️ pymobiledevice3 short-circuits when the status is already true. The two reboots are part of Apple's protocol, not incidental.

4. Linux-native iOS cross-compiler

poc/build_ipa.sh produces a signed .ipa on CachyOS/Arch using clang + ld64.lld + ldid — zero Apple/Xcode dependencies. Two steps per architecture slice (avoids the clang driver swallowing -arch/-platform_version when delegating to ld64.lld). Auto-detects toolchain, graceful arm64e → arm64 fallback.

Build & environment variables (click to expand)
sudo pacman -S clang lld zip && yay -S ldid
mkdir -p poc/SDK
git clone https://github.com/theos/sdks poc/tmp && mv poc/tmp/iPhoneOS*.sdk poc/SDK/iPhoneOS.sdk

cd poc && IOS_SDK=/path/to/iPhoneOS.sdk ./build_ipa.sh   # → EnableAMFIDevMode.ipa
VariableDefaultDescription
CLANGauto-detectPath to clang binary
IOS_SDKauto-detectPath to iPhoneOS.sdk
LD64auto-detectPath to ld64.lld linker
LDIDauto-detectPath to ldid (skipped if absent → unsigned)
MINIOS16.0Minimum iOS deployment target
SDKVERauto-detectSDK version for -platform_version

Note: the PoC's IOKit path (AppleMobileFileIntegrity selector 11) requires the platform-restricted entitlement com.apple.private.amfi.developer-mode-control — a non-Apple-signed binary is refused by the userclient. The supported way to enable Developer Mode is the lockdown protocol above. run_dvt.sh automates the alternative CoreDevice/RSD-tunnel deploy path (build works; on-device deploy WIP — see HANDOFF Session 12).

Findings Summary

ThreadResultDetails
AMFI Developer Mode (lockdown protocol)✅ Verified workingPersistent across reboot; FINDINGS_LOCK.md
AMFI dev-mode flag internals✅ DocumentedAMFI only reads; ACM is source of truth (cmd 0x25)
AMFI DER-entitlement patch✅ DocumentedBeta closes the DER-omission hole
AppleSEPUserClient dispatch map✅ Documented19 tables / 124 selectors; data/sep_full_table.csv
CVE-2025-43520 TOCTOU hypothesis❌ Closed — falseSession 15: key addresses misidentified heuristically
GPSCopy OOB write (ImageIO)❌ Closed — unreachableReal bug, silently patched, but zero callers in shipped userland
SpringBoard SBIconStateArchiver❌ Closed — robustness fixNew code written defensively; not type confusion
ImageIO ASTC/DDS hardening🔶 OPEN — flagshipDelivery chain mapped 2026-11-04: iMessage attachment → BlastDoor → IAKC container (first public documentation of the format) → mediaanalysisd → ASTC parser; zero-click iMessage candidate. Severity HIGH, conditional CRITICAL pending behavioral confirmation
CVE-2026-113915 race framework (MediaAnalysis)🔶 OPEN — new lead 2026-11-04TOCTOU windows mapped statically (audit-token check vs analysis-read, index-paired sandboxTokens); decompiles in research/intel/ma_decomp/race_*.c
rlebuf format-string lead🔶 OPEN — unlocalizedSee WRITEUP Session 25

Details in WRITEUP.md.

Documentation

Download Tool

Most Popular

View all →

Discover the most used tools by our community.

  • 1

    OsintHunter

    letox4/osinthunter

    🎯 The ultimate OSINT toolkit: investigation graph, confidence scoring, alias families, map, timeline and reports. 49 modules, 400+ sites, no API keys required.

    546
  • 2

    ghostlock-app

    yukonga/ghostlock-app

    GhostLock One-Tap Execution App (CVE-2026-43499)

    477
  • 3

    ARTEX

    baarai/artex

    LLM multi-agent autonomous penetration testing platform with planner/worker agents, asset and exploration graphs, MITM traffic recording, and vulnerability retesting.

    377
  • 4

    redforge

    cybersecurity91/redforge

    Browser-side red team toolkit with 102 offline tools for recon, payload generation, credential attacks, crypto, encoding and engagement reporting.

    324
  • 5

    estorides

    grisuno/estorides

    Aggregates 99+ free OSINT sources in parallel, resolves entities into a knowledge graph, and exports STIX 2.1, MISP, or GraphML with LLM-assisted analysis.

    269
  • 6

    CyberStrikeAI

    ed1s0nz/cyberstrikeai

    The system of action for AI-native cybersecurity—where intent becomes governed execution, evidence becomes operational memory, and every operation improves the next.

    252

Explore all tools

Browse our collection of tools

View all tools →