Skip to content

CTF field notes: the web category

A running log of web challenges: patterns that repeat, traps I fell into, and the meta-skill CTFs are secretly teaching.

planted October 5, 2025 · last tended May 30, 2026

Actively tended. Revisited often, links forming to other notes.


A perpetual note. Newest season at the top; lessons distilled as they stabilize.

Patterns that keep paying rent

  • Read the source like an attacker, not a reviewer. Reviewers ask “is this correct?” Attackers ask “what does this assume?” The gap between those questions is most flags, and it’s the whole thesis of the-attackers-mindset-is-systems-thinking.
  • The challenge title is a hint, every time. Puzzle authors can’t resist.
  • When stuck, enumerate trust boundaries. Client→server, server→database, service→service. The flag lives at the boundary the author hopes you’ll skim.

Traps I personally keep falling into

  • Going deep on the first idea instead of wide on five ideas. Thirty minutes per hypothesis, then rotate.
  • Forgetting that time is the score. There’s a bankroll-management flavor to this: allocating attention across challenges is a betting problem, which is what sent me down the kelly-criterion-for-bug-hunting rabbit hole.

Why bother with CTFs at all

They compress the feedback loop. Real-world offensive work pays out insight on a timescale of weeks; a CTF pays out in hours. Same muscle, faster reps, zero collateral. It’s the gym, not the sport.

Paths that lead here

Where this note points

More from these beds