Tactical LogHuntress CTF 2026 // team archive

Days / Day 03 / Script Analysis / Expansion Pack

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

Expansion Pack

Script Analysis SSTTMM Modes reported CORRECT in this write-up

Day 03 Script Analysis (Batch/JScript/PS1 static field extraction). GM id script-analysis-day-03-batch-expansion.

Method

  • Each attempt ships an AES zip (password infected) with 3 PS1, 9 JS, 9 CMD/BAT; mastery ships two such sets (ids prefixed set1./set2.).
  • PS1: base64 literal -> JSON. JS: run only inspect_*() in node with eval replaced by JSON.parse and ActiveXObject blocked. BAT: concatenate SET fragments (unescape ^|).
  • Role comes from the steps signature (relay-handoff is staged_chain, not relay).
  • Batch expansion/control labels come from the recovery region (between :HUNTRESS_SEPARATOR_DONE and echo(): control: for /l -> call_subroutine; goto :HUNTRESS_DISPATCH -> goto_dispatch; call :HUNTRESS_RECOVER -> call_subroutine; if errorlevel -> errorlevel_guard; if defined -> if_guard; else direct. expansion: call set with frag var h -> call_double; for %%G + call set -> for_indirect; else delayed.
  • GM rejects a whole batch if any field is wrong, banks accepted fields; submit byte-derived fields as one batch, then probe control/expansion per field (predicted value first, ~12 threads).
  • Timed windows after a retry are only ~7-30 s: the whole pipeline must be one automated run.

Scripts

scripts/solve_expansion.py, scripts/fast_mastery.py, scripts/check2.py (label regression).

Tokens

time_trial Token2c6ed6b96f562a420a149cff4f32bca1; mastery Token674f667a5f3e10f53ce6baf7f37ecd59.