Tactical LogHuntress CTF 2026 // team archive

Days / Day 09 / Script Analysis / All the World's a Stager

DAY 09//LANE: SCRIPT ANALYSIS//STATUS: CORRECT x3

All the World's a Stager

Script Analysis SSTTMM Modes reported CORRECT in this write-up

Challenge

  • Category: Script Analysis (Day 09). Game Master ID script-analysis-day-09-stager-relationships.
  • Prompt: "Every stager claims to know who came before it and who comes next. Build the relationship graph from final-byte evidence alone, and expose the stage whose claimed family tree is impossible."
  • Modes: Single Solve, Time Trial, Mastery - all CORRECT (3/3).
  • Answer form: 695 per-field answers (scenario / attack / url / wallet / adapter / relationship-graph fields). No flag{} wrapper.

Artifacts

  • The assigned AES zip of inert script fixtures for this attempt (password infected), analysed statically.

Triage

Script-inventory family (the recurring PS/JS/batch/bash/Node multi-field inventory). The Day-09 new layer is stage relationships: each fixture declares a predecessor/successor family tree, and the task is to reconstruct the graph from each fixture's final-byte evidence and find the one stage whose claimed lineage is impossible (a cycle or a contradiction).

Investigation

Solved by challenges/_lib/autosolve_script.py at claim: it decodes each fixture via its own self-describing Material_/Codec_ pipeline (never executing sinks), extracts the per-field inventory, and builds the predecessor/successor relationship graph from the final-byte markers to flag the impossible lineage. 695 fields were resolved offline from the fixtures' own bytes.

Flags (GM completion tokens)

  • single_solve Token71b8de03b9d4f224d99695e5025c93fd

(Time Trial and Mastery also CORRECT per the done-ledger; the autosolve record captured only the single-solve token - the timed modes were completed by the owning agent against each attempt's own bytes.)

Minimal Reproduction

wsl python3 challenges/_lib/autosolve.py 9 script-analysis-day-09-stager-relationships script-analysis - start, open the infected zip, decode each fixture by its own codec string, build the relationship graph, submit the per-field answers.

Lessons Learned

  • Same script-inventory spine as D02/D03/D06/D07, plus a relationship-graph layer. Do NOT execute fixtures; decode via each fixture's own Material_/Codec_ steps. The graph/"impossible family tree" twist is the day's one new layer; fold it into autosolve_script so it stays banked.