- Back Up a Minute
gm.start(challenge) returns one live target site per question (proof-1 for Single Solve/Time Trial; proof-1+proof-2 for Mastery, one target each). Target site: a small Node.js "Status Sprout" status page. ...
- Permission to Slip
Up to Day 19, the web lane had NEVER staged live - all web coverage was synthetic offline against the four web_contracts.py executors (hash, jwt, config, http). None of them covers: an id-bearing JSON API ...
- Query Me This
Day 3 - Web Exploitation - boolean-blind SQL injection in a search box - all three modes CORRECT on 2026-10-19 via the homestation Commander (same backlog pickup as Permission to Slip; agent-6 did not claim ...
- Administratively Speaking
Each mode gives one or more live target URLs under .2026.huntress.ctf.games. No downloadable artifact. The question in every mode is "Recover the proof from Target N", answer kind exact_text, normalization ...
- Stay in Your Directory
Both the Single Solve and Time Trial targets are a PHP app ("Runbook Nook" / "Stay in Your Directory") where a document viewer includes files relative to its own pages directory:
- Reflect Upon This
GET / shows a "Search Mirror" Fastify app. GET /api/clues returns the feature route (/execute-...), the callback route (/callback-...) and a per-target nonce. The feature route reflects the q parameter as ...
- Session Impression
scratchpad/si_solve.py runs the three-step attack for every target returned by the Session Impression start, maps answer_ids proof-N to targets by order, and submits in one batch. It worked for Single and ...
- Stored for Later
solved_by on all three is the shared team identity the team solver (expected).
- Forged With Care
Send the assigned target a cross-site GET with the active session cookie. Set the destination to the external review mailbox and omit csrf_token:
- Uploading Expectations
The GM supplies live targets in each mode’s start response. Each target was handled independently; the Mastery targets used three different web paths despite sharing the same challenge prompt.
- Ask Again Later
solved_by on all three is the shared team identity the team solver.
- Posted Too Much
The target is a NestJS/Express app. /api/clues is the per-attempt route map:
- Template Temper
Answer format for every target: exact_text, normalization trim — submit the verbatim proof_ string recovered from each target. Flags/proofs above are the GM-accepted values from ...
- Fetch Quest
Mastery is the real test: each of the 4 targets is a different web vuln bundled under the SSRF "Fetch Quest" theme. The Single and Time Trial variants are the same 4 archetypes, drawn in isolation.
- The API Has Opinions
Opened the Single target, read /, saw the hint "Open workspace notes" → /api/clues. /api/clues exposed feature_route, protected_reference; /api/inventory listed the field/action vocabulary. Enumerated (id ...
- Reset Expectations
Each target advertises its own routes: GET /api/clues -> {feature_route (submit), secondary_route (result), recovery_guide_route} GET /api/recovery -> {request_route, redeem_route, account_parameter ...
- Resolver Revolt
caseIndex labels one id as "reference only", but the case(id) resolver has NO visibility check: it returns the note for that id anyway. Query:
- Shell Company
/api/clues advertises feature_route (e.g. /process-38db5f), input_parameter (path), example_path (/app/static). The parameter is passed straight into a shell command (ls -ld $path), so ;/&&/| inject. ...
- Serialized Offender
Deterministic ladder, not an LLM guess. The whole family pool is now covered by challenges/_lib/web_proof_recon.recover(url) after the 2026-10-26 promotion (see §6). recover() walks the ladder and returns ...
- Trust the Webhook
This section is the solve itself, recorded from the run on our Homebase VM. The sections after it are the working notes from the earlier live attempt, kept as written; the blocker they describe was resolved ...
- Double Spent
GET /api/clues to resolve the per-target feature/secondary routes. Fire ~40 parallel POST /execute- requests (no body, no auth, no cookies). GET /audit- -> the response body carries evidence: proof_. Submit ...
- Forwarded Misgivings
solver_copy.py additions: _tech_forwarded_misgivings: /api/clues → feature_route → scoped_get(..., headers={"X-Forwarded-For":"127.0.0.1"}) → extract evidence → return proof. Walks a short header ladder ...
- Socket to Me
Target: https:/// (Koa app "Live Case Wire", role=analyst).
- Fail Open Friday
GET /api/clues on the assigned target. The response identified the feature route and documented the valid public decision shape: remote:: with a documented standard decision. Sending a MALFORMED value with ...
- If a Breach Falls in a Log
GET /api/clues to obtain the feature route + secondary audit route. POST {} to the feature route → response reports a completed protected_export and an export_id. GET the secondary (audit) route → find the ...
- Internal Affairs
Target: SS Target 1 Attempt ID: [attempt-id] Answer ID: proof-1 Timer: no deadline
- Trust the Build
Started through the Game Master with challenge ID web-exploitation-day-26-trust-the-build. The SS attempt ID was [id]. This is a web challenge, so the start response had no downloadable artifact; it ...
- Pass the Identity
The live target advertises itself at /api/clues:
- Queue the Confusion
GET /api/clues -> {feature_route, secondary_route, owner_directory_route, current_role: analyst}. GET /api/owners -> {caller: analyst, restricted_owner: executive}. POST with {"owner": "executive"} is ...
- Framework Roulette
Result: all three modes CORRECT by 13:51 ET on release day (Single Solve, Time Trial, Mastery with six accepted ids). Time Trial and Mastery were regular untimed attempts, not ranked. All three submits ...
- Full Stack Incident
The target exposed its own clues and request log. Those endpoints were the route map; the route names were randomized for this instance, so they should be read from /api/clues instead of guessed or hardcoded.