2026-10-12

Day 12: Pascal's Wager

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–d11 were answered as on Day 11.
  3. d12 format (the twist): earlier format questions accepted labels like ELF64. This one only accepts a lowercase token.
  1. d12 config: the question said to scan for a literal HCFG and accept the first valid record. The offset is where HCFG starts. Re-checked on the saved sample:
HCFG offset=82928 version=1 xor_key=0x81 len=368 crc32=0xe4fc81f8
section of match: .data
JSON: {"campaign":"BR12-000","domain":"node-000.day12.example.invalid","ipv4":"198.51.100.230","url":"https://node-000.day12.example.invalid/api/BR12-000","mutex":"Global\\HuntressBR12_000", ...}

Answers: d12_analysis_hcfg_offset = 82928, CRC32 0xe4fc81f8, campaign BR12-000.

  1. Submitted all 120 answers (answers.json). Result: CORRECT.
  2. Time Trial: a fresh variant, same steps. Result: CORRECT.
  3. Mastery: three deliveries (360 answers), same steps. Result: CORRECT.

Results

ModeResultFlag
Single SolveCORRECT986b8f546ed5eac11c6cc89ad42acf7b
Time TrialCORRECTadd234c992bc28660a08418a81bd8e3e
MasteryCORRECT990b9df627fb66a0a921393c0c745ee9

Each mode folder has the raw start-response.json, answers.json, submit-response.json and final-status-response.json. The downloaded zips are under deliveries/.

Reproduce

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

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

Checked on 2026-11-01: this gives the same 120 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-12-pascal-archive-stager single_solve /tmp/d12

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

Day 12: Managed Expectations

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 MVID lives in the CLR metadata, in the #GUID heap. Rebuilds get a new MVID. Renamed copies keep the old one.

  1. Wrote an MVID reader and checked it on the Single Solve DLL, then added it to run_meta.py:
  2. Find the metadata root signature BSJB.
  3. Read the version-string length at BSJB + 12. Skip the version string (padded to 4 bytes).
  4. Read the stream count. Walk the stream headers: offset (4 bytes), size (4 bytes), NUL-ended name padded to 4 bytes.
  5. At the #GUID stream, take the first 16 bytes.
  6. Print it as a GUID. The first three parts are little-endian.
if name == b'#GUID':
    g = b[i+off : i+off+16]          # i = offset of 'BSJB'
    return '%08x-%04x-%04x-%04x-%012x' % (
        struct.unpack('<I', g[0:4])[0], struct.unpack('<H', g[4:6])[0],
        struct.unpack('<H', g[6:8])[0], struct.unpack('>H', g[8:10])[0],
        int.from_bytes(g[10:16], 'big'))
  1. Single Solve. managed-001.dll → 21e410f3-c977-465c-80eb-6890ddd3085c. CORRECT.
  2. Time Trial. managed-002.dll → 9e0e197f-d610-4ec9-bd1c-d28da985893a. CORRECT.
  3. Mastery. managed-003.dll → 2658bcc7-f07c-48b1-8cb9-2bb645f8680e, managed-004.dll → ecc37f87-9668-43c5-b9f4-011ee0d07c7c. CORRECT.

Results

ModeResultFlag
Single SolveCORRECT3730fd111f2f272740d3eb0799a96ca0
Time TrialCORRECTe11b227c3b1709eb339085723afba36f
MasteryCORRECTcdd3449477126525d063f46c62a7015b

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-12-managed-expectations single_solve /tmp/d12

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 parses the DLL bytes. It never loads or runs them.

Day 12: SQLite Assumptions

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 hex (also used on Day 6).
{"schema":"huntress.mobile.puzzle.v1","day":12,"codec":"hex","data":"414e532d30333946304439303731313131303530"}
  1. Decoded it. Each pair of hex digits is one ASCII character:
import json
p = json.load(open('single-solve/huntress_puzzle.json'))
print(bytes.fromhex(p['data']).decode())

Output: ANS-039F0D9071111050.

  1. Ran the lane driver for all three modes:
python3 -I ~/.config/huntress/solvers/run_mode.py mobile-android-day-12-sqlite-assumptions <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-039F0D9071111050), Time Trial (ANS-668B39E20D9A458F) and all three Mastery answers came back CORRECT.

Results

ModeResultFlag
Single SolveCORRECT2e1400512f174a77409341aea09848b7
Time TrialCORRECT65a16fa4819e3f76c51a7fdfbcb4c854
MasteryCORRECT0df1f9bf63c6c4677372bc4e8a343068

Each mode folder has answers.json, start-response.json, submit-response.json and final-status-response.json. The saved Time Trial start-response.json also carries a start_required error message, but its submit-response.json is CORRECT. 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-12-sqlite-assumptions single_solve mobile_puzzle /tmp/d12

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 12: AutoIt Takes Two

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. Checked whether AutoIt was a new family. It was not: the files are polyglot-autoit-*.au3 with the usual marker, so the existing polyglot path handled them.
  1. Submitted. The Single Solve was CORRECT (855/855).
  1. Real answers from single-solve/answers.json:
{
 "polyglot-autoit-launcher-role": "launcher",
 "polyglot-autoit-launcher-attack": "T1059",
 "polyglot-autoit-launcher-adapter": "process_builder",
 "polyglot-autoit-launcher-campaign": "AUTOIT-02a74447",
 "polyglot-autoit-launcher-url": "https://autoit-02a744470e.example.invalid/stage",
 "polyglot-autoit-launcher-stage-count": "3",
 "polyglot-autoit-launcher-steps": "decode_embedded>write_file>dispatch_process",
 "polyglot-autoit-launcher-host-profile": "standalone"
}
  1. Time Trial and Mastery used the same solver on fresh variants.

Results

ModeResultFlag
Single SolveCORRECT4bb887a602c4fe4b704fe49fac17770f
Time TrialCORRECT1e04c64e531777019c267a857ad8a919
MasteryCORRECTd2659c3b7978a4b6b48246c3dc815114

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/d12/ex
7z x -pinfected -o/tmp/d12/ex repos/day-12-script-analysis-autoit-takes-two/single-solve/evidence.zip
python3 -I tools/solve_expansion.py /tmp/d12/ex \
  repos/day-12-script-analysis-autoit-takes-two/single-solve/start-response.json /tmp/d12/answers.json

This rebuilds all 855 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 12: Back at You

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. The entire text is reversed. Read it backwards.
  2. Mastery blobs use multiple encodings from Days 1-12. 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