2026-10-09

Day 9: Nimble

Lane: Binary reverse engineering. Modes: Single Solve, Time Trial, Mastery. Result: all CORRECT.

The challenge

What we were given

What was asked

How it was solved, start to finish

  1. Ran the driver run_tm.py: start the attempt, download the zip, run solve_tm.py, submit.
  2. d01–d08 were answered as on Day 8.
  3. d09 config: the question said to Base64-decode every run of 100+ Base64 characters, and accept the first one that decodes to a CRC32-valid HCFG record.
  1. d09 offset (new): for a Base64 config, the offset is where the Base64 string starts in the file (for a raw record it would be where HCFG starts). solve_tm.py already returned the match position from its Base64 scan, so it answered hcfg_offset with that number.

Re-checked on the saved sample:

[base64 run at file offset 30696, run length 508]
HCFG version=1 xor_key=0x51 len=368 crc32=0x9614e1a8
section of match: .rodata
JSON: {"campaign":"BR09-000","domain":"node-000.day09.example.invalid","ipv4":"198.51.100.180","url":"https://node-000.day09.example.invalid/api/BR09-000","mutex":"Global\\HuntressBR09_000", ...}

Answers: d09_analysis_hcfg_offset = 30696, CRC32 0x9614e1a8, campaign BR09-000, format ELF64.

  1. Submitted all 90 answers (answers.json). Result: CORRECT.
  2. Time Trial: a fresh variant, same steps. Result: CORRECT.
  3. Mastery: five deliveries (450 answers), same steps. Result: CORRECT.

Results

ModeResultFlag
Single SolveCORRECT8e66d681780cc49c103f5fbc868d339e
Time TrialCORRECT167789090a984d148551749a1c78d81a
MasteryCORRECT1d8cfbfdf1875b3790f04a187db958a8

Each mode folder has the raw start-response.json, answers.json, submit-response.json and final-status-response.json.

Reproduce

Offline, from this folder (no Game Master needed):

mkdir -p /tmp/d09/deliveries && cp single-solve/evidence.zip /tmp/d09/deliveries/delivery-1.zip
python3 -I ~/.config/huntress/solvers/solve_tm.py single-solve/start-response.json /tmp/d09/deliveries /tmp/d09/answers.json

Checked on 2026-11-01: this gives the same 90 answers as answers.json. It only parses the samples and never runs them.

Live driver:

python3 -I ~/.config/huntress/solvers/run_tm.py binary-reverse-engineering-day-09-nim-generated-runtime single_solve /tmp/d09

This needs a Game Master token in ~/.config/huntress/gm-token.

Day 9: Built Different

Lane: Metadata forensics. Modes: Single Solve, Time Trial, Mastery. Result: all CORRECT.

The challenge

What we were given

What was asked

How it was solved, start to finish

  1. Read the new question. It asks for the CPU type field of a Windows PE file. That is the 2-byte Machine field in the COFF header.
  2. Added a handler to run_meta.py. The PE header offset (e_lfanew) is the 4-byte value at 0x3C. The header starts with PE\0\0, so Machine is at that offset + 4:
if 'pe-coff-machine' in aid:
    pe = struct.unpack_from('<I', fb, 0x3c)[0]
    return '0x%04x' % struct.unpack_from('<H', fb, pe + 4)[0]
  1. Ran run_meta.py for all three modes (a helper agent ran the metadata lane). Every other field used the handlers from Days 7–8.
  2. Answers. telemetry-agent-001.exe gave 0x014c (x86) in the Single Solve, the Time Trial and all five mastery sets.
  3. Submitted all answers in one JSON object per mode. The Game Master replied CORRECT and returned the flag.

Results

ModeResultFlag
Single SolveCORRECT9cc376d12c158369ca7e25281e10b837
Time TrialCORRECT5a1873f08b5871768d3be26aada54110
MasteryCORRECTbaadf6dc65205496afe0ea1d7b07a004

Each mode folder has answers.json, start-response.json, submit-response.json and final-status-response.json. The Single Solve folder also has the zip. No screenshots were captured.

Reproduce

python3 -I ~/.config/huntress/solvers/run_meta.py metadata-forensics-day-09-built-different single_solve /tmp/d09

This needs a Game Master token in ~/.config/huntress/gm-token. For time_trial and mastery it calls op=retry first, which spends one of the unique attempts. It reads the PE header bytes. It never runs the .exe.

Day 9: Trust Everyone

Lane: Mobile (Android). Modes: Single Solve, Time Trial, Mastery. Result: all CORRECT.

The challenge

What we were given

What was asked

How it was solved, start to finish

The app was never installed or run.

  1. Started the Single Solve and downloaded the APK.
  2. Read the puzzle asset. The codec is base64 (also used on Day 3).
{"schema":"huntress.mobile.puzzle.v1","day":9,"codec":"base64","data":"QU5TLTNEM0I4MDM5NTI0MEI4RUU="}
  1. Decoded it:
import json, base64
p = json.load(open('single-solve/huntress_puzzle.json'))
print(base64.b64decode(p['data']).decode())

Output: ANS-3D3B80395240B8EE.

  1. Ran the lane driver for all three modes. A helper agent ran it once per mode:
python3 -I ~/.config/huntress/solvers/run_mode.py mobile-android-day-09-trust-everyone <mode> mobile_puzzle <workdir>

The driver downloads each APK, reads its puzzle, decodes it by its codec, and submits all answers at once.

  1. Results: Single Solve (ANS-3D3B80395240B8EE), Time Trial (ANS-31B3DA8804F7211C) and all five Mastery answers came back CORRECT.

Results

ModeResultFlag
Single SolveCORRECT492626431b00af6000167c720d9a296d
Time TrialCORRECTe6fd3ecd2e57a363cd0963d5bec39178
MasteryCORRECT18015a829f1112b61d38a3d4fcbae877

Each mode folder has answers.json, start-response.json, submit-response.json and final-status-response.json. No screenshots were taken.

Reproduce

Offline: run the Python snippet above from this folder.

A fresh run with the driver:

python3 -I ~/.config/huntress/solvers/run_mode.py mobile-android-day-09-trust-everyone single_solve mobile_puzzle /tmp/d09

This needs a Game Master token in ~/.config/huntress/gm-token. It only unzips the APK and reads the asset. It never installs or runs the app.

Day 9: All the World's a Stager

Lane: Script analysis. Modes: Single Solve, Time Trial, Mastery. Result: all CORRECT.

The challenge

What we were given

What was asked

How it was solved, start to finish

  1. Started the untimed Single Solve and downloaded evidence.zip. Extracted it with 7z x -pinfected.
  2. Ran the existing solver (solve_expansion.py, driven by run_expansion.py). Each family has its own decoder:
FamilyFilesHow the config is recoveredFirst seen
PowerShell*-sample.ps1Base64 JSON inside FromBase64String('...')Day 1
JScript*.jsjsdec.js loads the fixture in a Node vm sandbox (pure-computation globals only) and calls its decode functionsDay 3
Batch*.bat, *.cmdjoins the :HUNTRESS_INSPECT fragments and drops ^ caretsDay 3
VBScript*.vbsMaterial_ + Codec_, transform search until the text starts `v=1\steps=`Day 4
Python*.pyMATERIAL_ read with ast.literal_eval, same transform searchDay 5
Bash*.shquoted Material_ + Codec_; "advanced" files start `v=1\feature=`Day 6, Day 7
Node.jsnode-*.mjsMaterial_ + Codec_ with \x, \u and hex-array formatsDay 7
host, polyglothost-*, polyglot-*HUNTRESS_ANALYSIS_V1:<ENC>-<data> marker (B64, HEX, HB64, FRAG)Day 8

Role comes from the ordered steps, and ATT&CK from the role and the language (rules in Day 3). Host and polyglot configs already contain their role and ATT&CK ID.

  1. The new files needed no new code. The Lua and SCT files carry the same HUNTRESS_ANALYSIS_V1 marker as Day 8, so hostpgdec.py decoded them as-is. The new Bash files are more "advanced" files (Day 7 rules).
  1. Submitted. The Single Solve was CORRECT with all 695 answers on the first run.
  1. The other four lanes of the day were solved in parallel by sub-agents while this lane ran.
  1. Real answers from single-solve/answers.json:
{
 "host-sct-scriptlet-jscript-role": "launcher",
 "host-sct-scriptlet-jscript-attack": "T1059",
 "host-sct-scriptlet-jscript-adapter": "process_builder",
 "host-sct-scriptlet-jscript-campaign": "JSCRIPT-6d31f81b",
 "host-sct-scriptlet-jscript-url": "https://jscript-6d31f81bec.example.invalid/stage",
 "polyglot-lua-downloader-role": "downloader",
 "polyglot-lua-downloader-attack": "T1105",
 "polyglot-lua-downloader-adapter": "http_client",
 "polyglot-lua-downloader-campaign": "LUA-4dafa916",
 "polyglot-lua-downloader-url": "https://lua-4dafa91644.example.invalid/stage"
}
  1. Time Trial and Mastery used the same solver on fresh variants.

Results

ModeResultFlag
Single SolveCORRECTab97d26f81ba912ac4de743f02ee1eff
Time TrialCORRECT04aba00d2b995c023bf7306e5aa408a3
MasteryCORRECT54d244888d245b5519d8147e3edcb7d0

Each mode folder has answers.json and the Game Master JSON. The Single Solve folder also keeps evidence.zip. No screenshots were taken.

Reproduce

Offline, from the repo root:

mkdir -p /tmp/d09/ex
7z x -pinfected -o/tmp/d09/ex repos/day-09-script-analysis-all-the-worlds-a-stager/single-solve/evidence.zip
python3 -I tools/solve_expansion.py /tmp/d09/ex \
  repos/day-09-script-analysis-all-the-worlds-a-stager/single-solve/start-response.json /tmp/d09/answers.json

This rebuilds all 695 saved answers (re-checked on 2026-11-01). It only parses the files. The tools/ copy decodes JScript with the pure-Python jsdec_py_emu.py, not the Node sandbox.

On the day, run_expansion.py drove the live modes. Since Day 23 that driver sends any question set with polyglot- IDs to solve_day23.py, which does not handle this format's host- and resource- IDs. So use solve_expansion.py directly, as above.

Day 9: Escape Room

Lane: Warmups. Modes: Single Solve, Time Trial, Mastery. Result: all CORRECT.

The challenge

What we were given

How it was solved

  1. Decode the blob. JSON-style \uXXXX escapes. Decode as unicode_escape.
  2. Mastery blobs use multiple encodings from Days 1-9. The solver (warmup_decode.py) tries every known decoder on each line and picks the one producing printable text.
  3. Concatenate all decoded lines. The text contains a message ending in the answer slug.
  4. Submit the slug to the Game Master.

Results