I'm a self-taught security researcher. No degree, no bootcamp — I started by opening binaries I wasn't supposed to understand and refusing to close them until I did. Reverse engineering, binary exploitation, and the occasional weekend lost to a CTF.
This site is where I write that work down. Partly so I stop forgetting things I already figured out once at 3am, partly because the writeups that taught me the most were people doing exactly this: showing the boring middle of the problem, not just the flag at the end.
what you'll find here#
Mostly long-form technical writeups — heap internals, anti-debug, devirtualizing obfuscators, fuzzing notes, kernel pwn when I'm brave. I try to show the dead ends too, because the dead ends are where the actual learning hides.
No newsletter, no "10 tools every hacker needs", no engagement bait. If a post is short it's because the idea was small, not because I'm chasing a posting streak.
how this site is built#
Plain Markdown, one Python script, no framework and no build server you have to trust. The whole thing is a folder of text files that compiles to static HTML. You can read every line of it. That's deliberate — a blog about taking software apart shouldn't be a black box itself.
reaching me#
Best over email or whatever's linked below. I read everything, I reply to most things, and I'm always down to talk shop about a gnarly target.
uid=1337(segfault) gid=1337 groups=re,pwn,ctf
interested in: glibc internals, VM-based obfuscation, fuzzing, kernel pwn
currently nerd-sniped by: anti-debug tricks and packer devirtualizationpersonal: github twitter email
the scene: pwn.college ctftime shellphish