trust the webhook: body aliases before trust headers
huntress ctf 2026, day 26 · web exploitation · all three modes
tools used: live web target capture, saved web inspection, and timed-attempt pipeline.
the target's clue supplied an event type, an owner scope and a feature route. the successful request was a flat json body carrying those observed values under the route's alternate field names.
challenge shape
single and time trial assigned one target each. mastery assigned multiple independently captured targets, which could mix web families. each proof belonged to its own target.
artifact anatomy
a clue response identified the current event type, owner scope and feature route. the handler distinguished a rejected webhook from a consumed event. the page and robots document did not disclose a signing key.
extraction method
read the clue on the assigned origin, build a flat event body with the observed event and scope under their documented aliases, and post it to the clue's feature route. accept a proof only from a consumed-event response.
validation and answer formatting
every route must remain on the assigned origin. current target values are read again in each mode, and a successful status alone is insufficient. a proof is submitted only when the response contains it. submitted results are [redacted].
failed approaches and pivots
several guessed trust headers and signature flags returned webhook_rejected. the body vocabulary, rather than an invented signing scheme, was decisive. the local worker could not save its edit during the race, and another team won the first two modes.
automation across modes
the collector classifies every target independently and keeps each proof paired with its answer id. the same evidence order is applied to each fresh time-trial or mastery target.
lessons
- read the route's body vocabulary before trying an unobserved trust mechanism.
- keep routes, parameters and ids local to the target that supplied them.
solve times
public scoreboard · day 26 finish: below top 10
- 17:44.7single#51 of 148 solvers
- 18:33.4time trial#48 of 144 solvers
- 19:21.9mastery#48 of 142 solvers
- #32team day finishof 135 teams that cleared it, in 19:21.9
- #7single orderof the day's 7, by our flag time
from the public scoreboard: 09:00 et release to our flag; the table below counts from our attempt's start.
the recorded work began with the assigned target. external completions and missing local winning captures are marked as such.
| mode | work to flag | attempts | wrong submits |
|---|---|---|---|
| single | not recorded | not recorded | 0 recorded |
| time trial | not recorded | not recorded | 0 recorded |
| mastery | not recorded | not recorded | 0 recorded |
the clock
a winning assignment deadline was not retained in the reviewed evidence for each mode; the work-to-flag figures above come from the day timeline where available.
| mode | time available | time used | time left |
|---|---|---|---|
| time trial | not recorded | not recorded | not recorded |
| mastery | not recorded | not recorded | not recorded |
where we got stuck
- several guessed trust headers and signature flags returned
webhook_rejected. the body vocabulary, rather than an invented signing scheme, was decisive. the local worker could not save its edit during the race, and another team won the first two modes.
flags: single, time trial, and mastery [redacted].
{generated by a clanker}