2026-10-17

Day 17: Decoder Ring

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. Added one handler per new question type to solve_tm.py. Each reads the bytes directly:
  1. Offsets: the solver reports where the winning record starts. For Base64 that is the start of the Base64 string. Examples: d08 18366768, d11 368272, d12 82928, d14 4000.
  2. hcfg_storage (new): the question gave ordered rules. The solver remembers how it found each record and maps that to a label:
  1. d17 config: a literal record. Re-checked on the saved sample:
HCFG offset=207432 version=1 xor_key=0x73 len=367 crc32=0x265cc435
section of match: .rodata
JSON: {"campaign":"BR17-000","domain":"node-000.day17.example.invalid","ipv4":"198.51.100.70","url":"https://node-000.day17.example.invalid/api/BR17-000","mutex":"Global\\HuntressBR17_000", ...}

Answers: format elf, XOR key 0x73, version 1, hcfg_offset 207432, campaign BR17-000.

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

Results

ModeResultFlag
Single SolveCORRECT2b2e663fe01c717c3f15c16f580f5612
Time TrialCORRECTdc17792a53355d0e48c65ea2868638a9
MasteryCORRECTd16a2d986626d89a7c13cd2bda45cf8d

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/d17/deliveries && cp single-solve/evidence.zip /tmp/d17/deliveries/delivery-1.zip
python3 -I ~/.config/huntress/solvers/solve_tm.py single-solve/start-response.json /tmp/d17/deliveries /tmp/d17/answers.json

Checked on 2026-11-01: this gives the same 204 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-17-encoded-configuration-recovery single_solve /tmp/d17

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

Day 17: Hear Me Out

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

The method: the file extension says .wav, but the codec must come from the stream itself. ffprobe reads the container and reports the codec without playing anything.

  1. Checked the Single Solve file with ffprobe. It reported pcm_s16le (16-bit little-endian PCM).
  2. Added an ffprobe handler to run_meta.py. It writes the bytes to a temp file and asks for the codec of audio stream 0:
r = subprocess.run(['ffprobe', '-v', 'quiet', '-select_streams', 'a:0',
                    '-show_entries', 'stream=codec_name', '-of', 'csv=p=0', tf.name],
                   capture_output=True, text=True, timeout=30)
return r.stdout.strip() or None
  1. Single Solve. Submitted pcm_s16le. CORRECT.
  2. Time Trial and Mastery. Helper agents ran run_meta.py for each lane. It answered all 22 and all 110. The codec was pcm_s16le in every set. Example synthesis answer (Time Trial): ["managed-001.dll","evidence-note.txt","panel-001.png","audio-001.wav"]. Both CORRECT.

Results

ModeResultFlag
Single SolveCORRECT93951605ab6c2622720720f0b4329257
Time TrialCORRECTd513d60db37e4442e23a8d568b861bcf
MasteryCORRECTe33de67dafb180b78ee04f1a23dc66b5

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; its saved submit says already_solved because it is a re-run, and the final status shows CORRECT. No screenshots were captured.

Reproduce

ffprobe -v quiet -select_streams a:0 -show_entries stream=codec_name -of csv=p=0 audio-001.wav
python3 -I ~/.config/huntress/solvers/run_meta.py metadata-forensics-day-17-hear-me-out single_solve /tmp/d17

The second line 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. ffprobe only reads the container headers.

Day 17: Name Collapse

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. New codec today: indexed. Each character of the code is shuffled to a new place.
{"schema":"huntress.mobile.puzzle.v1","day":17,"codec":"indexed","data":"-2FE1A2D163AA1N51SC0",
 "order":[3,10,17,4,11,18,5,12,19,6,13,0,7,14,1,8,15,2,9,16]}
  1. Put the characters back. order[i] is the output position of data[i]. For example data[0] is -, and order[0] is 3, so - goes to position 3.
import json
p = json.load(open('single-solve/huntress_puzzle.json'))
out = [None] * len(p['order'])
for i, pos in enumerate(p['order']):
    out[pos] = p['data'][i]
print(''.join(out))

Output: ANS-E26A5C21D3110FA1.

  1. Taught the driver. The same indexed logic went into mobile_puzzle() in run_mode.py.
  2. Ran the lane driver for all three modes:
python3 -I ~/.config/huntress/solvers/run_mode.py mobile-android-day-17-name-collapse <mode> mobile_puzzle <workdir>
  1. Results: Single Solve (ANS-E26A5C21D3110FA1), Time Trial (ANS-C30EEFE8AD4BFA35) and all five Mastery answers came back CORRECT.

Results

ModeResultFlag
Single SolveCORRECT67b61cdbd582ff52468fc2bd760a1cf7
Time TrialCORRECT499a2b7dfeb34fa590c20ffe24c3caf3
MasteryCORRECT55a3083d5eaeded27af5134556cac1cd

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-17-name-collapse single_solve mobile_puzzle /tmp/d17

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 17: Fetch Quest

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. No new code was needed. The AutoHotkey files carry the usual marker.
  1. A sub-agent ran all three modes (one agent per lane that day). It reported all three CORRECT.
  1. Real answers from single-solve/answers.json:
{
 "polyglot-auto_hotkey-staged-chain-role": "staged_chain",
 "polyglot-auto_hotkey-staged-chain-attack": "T1059",
 "polyglot-auto_hotkey-staged-chain-adapter": "operation_graph",
 "polyglot-auto_hotkey-staged-chain-campaign": "AUTO_HOTKEY-d950bfce",
 "polyglot-auto_hotkey-staged-chain-url": "https://auto_hotkey-d950bfcec0.example.invalid/stage",
 "polyglot-auto_hotkey-staged-chain-stage-count": "2",
 "polyglot-auto_hotkey-staged-chain-steps": "decode_configuration>return_configuration",
 "polyglot-auto_hotkey-staged-chain-host-profile": "standalone"
}
  1. Time Trial and Mastery used the same solver on fresh variants.

Results

ModeResultFlag
Single SolveCORRECTb6a64386dafa6bd292f301db4c3b7704
Time TrialCORRECT15627e030030f7c6653af8c6cef93e52
MasteryCORRECT2972bddae28cb029d938956e4ac16c0e

Each mode folder has answers.json and the Game Master JSON (start-, submit-, final-status-response.json). The evidence archives were not kept. No screenshots were taken.

Reproduce

The evidence archive was not kept, so the saved answers cannot be rebuilt offline. For a fresh attempt of this format:

mkdir -p /tmp/d17/ex
7z x -pinfected -o/tmp/d17/ex evidence.zip
python3 -I tools/solve_expansion.py /tmp/d17/ex start-response.json /tmp/d17/answers.json

Then submit answers.json to the Game Master (needs a token in ~/.config/huntress/gm-token). 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 17: Bacon Bits

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. Groups of 5 a/b letters each map to a 4-bit hex nibble, then hex-decode to ASCII.
  2. Mastery blobs use multiple encodings from Days 1-17. 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