Tactical LogHuntress CTF 2026 // team archive

MISSION OVERVIEW//HUNTRESS CTF 2026//TEAM: SECURENETMD//FINAL: 38TH

Thirty-one days on the plot

A month of daily challenges, run as team SecureNetMD. I invited others, but no one participated or assisted in any stage of this event; so the work fell to me and Claude - 16+ hours a day, every day, learning, solving and improving as it went. These are the write-ups I kept while it happened, with the setup that produced them and what it taught me.

38th
Final placement
Huntress CTF 2026, October 1-31
31
Release days
31 with archived write-ups
189
Write-ups
one per challenge, written during the event
544
Modes reported correct
186 Single / 180 Time Trial / 178 Mastery

Tactical plot NAV // DAYS

Lanes NAV // LANES

LaneWrite-upsSingle SolveTime TrialMastery
Warmups32313029
31312929
Mobile Android31302929
Script Analysis31313131
Binary RE32313030
Web Exploitation31313130
Other1100
Total189186180178

Mode columns count write-ups that report that mode CORRECT in their own text (parsed automatically; a write-up that only says "solved" is not counted).

Headline lessons LOG // DEBRIEF

  1. 01
    First contact is the speed.

    When a lane's deterministic solver already knew the day's shape, a mode landed in one to three seconds. When it did not, the same mode cost an agent anywhere from seconds to half an hour. Almost every speed gain came from raising the share of modes the solver handled on first contact.

  2. 02
    Every lane was yesterday plus one layer.

    The daily challenges in a lane shared a spine and added one new container, encoding or language each day. Once we wrote that down as data and predicted the next layer, we could prebuild for it the night before instead of meeting it cold at release.

  3. 03
    Exact strings, no partial feedback.

    The grader compares exact text and rejects a whole batch if one field is off, without saying which. Banking every accepted value and format (hex width, casing, braces) turned a guessing game into a lookup.

  4. 04
    A thirty-second window forgives nothing.

    On Day 11 the release-time rate limiting made our retry backoff sleep straight through a timed window, and a lost Time Trial also locked the Mastery behind it. Afterwards every timed start became a hard time budget, preceded by a free status check of how many attempts remained.

  5. 05
    Derive from this attempt's bytes.

    Timed material rotated per attempt. Reusing an old answer was never safe; only a solver that read the current artifact was.

  6. 06
    One owner per mode.

    With two stations and shared attempts, two runners on one mode could burn a scarce ranked attempt. Atomic claims and static lane ownership kept that from happening.

  7. 07
    A model in the hot path sets a floor.

    Each agent decision is a model turn. The fastest teams cleared a full day in minutes with plain scripts dispatching to solvers; our agents were best used for triage and for extending solvers, not for executing every step. A full reverse-engineering special (Day 30) was a different class entirely: hours, not seconds.

Late-event contacts LOG // RECENT

All 189 write-ups >   How we were set up >   The Game Master contract >