This notebook is the working file of a reversing / vulnerability-analysis practice, not a link blog.

What a note contains

If a page does not have tool output, a figure, and a sanitized reproduction, it is unfinished.

Typical skeleton:

  1. Lab binary or APK I compiled (or a public CVE class, not a stolen sample)
  2. readelf / otool / jadx / gdb / lldb / Frida transcript
  3. ARM64 or x64 disassembly of the one function that matters
  4. Reproduction that stops at crash, ASAN, or a redacted trace
  5. The patch or the detection check I would actually ship

Secrets, load addresses, team IDs, and tokens are [REDACTED] or truncated.

Tracks

  • Network Security — parsers, auth tokens, HTTP framing, TLS metadata
  • Binary Analysis — ELF/Mach-O/JNI, GOT/PLT, ObjC, vtables
  • Operating Systems — tokens, Kerberos fields, containers, kernel invariants (no LPE recipes)

What I will not paste

Working exploit chains, FairPlay unwrap, jailbreak AMFI bypasses, or live credentials. The lab memcpy that ASAN flags is here so the write-up has a crash; a shell is not.