hello, writeups
A lab notebook, made public. Why this exists, what will show up here, and the rules it runs by.
Why write it down
Solving a box feels like understanding. Explaining the solve to someone else is the actual test — half the time the writeup is where I discover I got the flag without getting the why. So everything I break, build, or study on the security track gets a page here, written the way I'd want to read it: what I tried, what failed, what finally worked, and what I'd do faster next time.
What lands here
- CTF and TryHackMe room writeups — recon to root, dead ends included.
- Course notes from the security fundamentals I'm working through right now.
- Build logs from security tooling like Crypt.
- The occasional crossover from the AI line — agents meet security more often than you'd think.
House rules
- No spoilers for active competitions or paid content — writeups publish after rooms retire or events close.
- Flags and final payloads sit behind spoiler folds, so you can read the method and still do the box yourself.
- Everything here was done on targets I'm authorised to test: practice labs, CTFs, my own machines.
- Honest logs — if I burned an hour in a rabbit hole, the rabbit hole gets documented.
Colophon
Same site, same rules: hand-written HTML, no frameworks, no build step. Each post is one file. Code blocks look like this:
$ nmap -sC -sV -oN scans/initial 10.10.x.x
# enumerate first. always enumerate first.…and anything that would spoil a box looks like this:
spoiler — the flag format
Not an actual flag. But this is where one would live.