Structured writeups of CTF rooms/challenges, written the way I'd document a real engagement: recon → exploitation → privilege escalation → remediation, with MITRE ATT&CK mapping where it applies. Flags are redacted per each platform's sharing guidelines — the point of a writeup is the methodology, not the flag string.
This repo pairs with OWASP-Top10-Labs
(vulnerability classes in depth) and SOC-Lab-Playbooks
(defender-side response) — this repo is the attacker-side complement.
| Platform | Room / Challenge | Category | Key technique |
|---|---|---|---|
| TryHackMe | Blue | Windows exploitation | EternalBlue (MS17-010) |
| TryHackMe | Pickle Rick | Web / Linux | Command injection → privesc |
| TryHackMe | Bounty Hunter | Web / Linux | XXE → Python library hijack |
| picoCTF | Wave a flag | General skills | Binary usage/help enumeration |
| picoCTF | Mod 26 | Cryptography | Caesar cipher / ROT-N |
| picoCTF | Insp3ct0r | Web exploitation | Client-side source review |
More added as I work through additional rooms/boxes — see
docs/methodology.md for the approach and
docs/writeup-template.md for the format every
writeup follows.
Most public writeups are a stream-of-consciousness terminal log. These follow a fixed structure instead — Recon / Exploitation / Privilege Escalation / Remediation / ATT&CK Mapping — because that's the shape a real pentest report or vulnerability disclosure takes, and it's the habit worth building.