2026-10-10

Day 10: Zig Zag

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–d09 were answered as on Day 9.
  3. d10 config: the question said to scan the file for literal HCFG and accept the first valid record.

Re-checked on the saved sample:

HCFG offset=132160 version=1 xor_key=0x61 len=368 crc32=0xceda03ad
section of match: .hcfg
JSON: {"campaign":"BR10-000","domain":"node-000.day10.example.invalid","ipv4":"198.51.100.200","url":"https://node-000.day10.example.invalid/api/BR10-000","mutex":"Global\\HuntressBR10_000", ...}
  1. d10 section check (new): added has_hcfg_section to solve_tm.py:
  1. Submitted all 100 answers (answers.json). Examples: d10_analysis_has_hcfg_section = true, d10_analysis_config_crc32_hex = 0xceda03ad. Result: CORRECT.
  2. Time Trial: a fresh variant (campaign BR10-007), same steps. Result: CORRECT.
  3. Mastery: three deliveries (300 answers). Sets 2 and 3 had the PE build of d10 (campaigns BR10-001 and BR10-006). The format and machine code reads ELF and PE headers alike, so the same steps worked. Result: CORRECT.

Results

ModeResultFlag
Single SolveCORRECTd78c629de45c9048c1a19b904fcf4d97
Time TrialCORRECT1bd84a8a046cfcd0cc66288022efea17
MasteryCORRECTc6e1925c9b17409c5f7d68d7ab26ae12

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

Checked on 2026-11-01: this gives the same 100 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-10-zig-cross-platform-services single_solve /tmp/d10

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

Day 10: Where Do We Begin?

Lane: Metadata forensics. Modes: Single Solve, Time Trial, Mastery. Result: all CORRECT (the Single Solve flag was not recorded).

The challenge

What we were given

What was asked

How it was solved, start to finish

  1. Added a handler to run_meta.py. AddressOfEntryPoint is a 4-byte field in the optional header, at PE header offset + 0x28:
pe = struct.unpack_from('<I', fb, 0x3c)[0]          # e_lfanew
rva = struct.unpack_from('<I', fb, pe + 0x28)[0]    # AddressOfEntryPoint
  1. First Single Solve submit failed. The metadata helper agent also hit HTTP 409 errors, because several agents were calling the Game Master at once. Run again by hand, the driver computed 0x65bd0 for telemetry-agent-001.exe. The Game Master said incorrect. That reply is the one saved in submit-response.json.
  2. Found the format by testing one value at a time:
0x65bd0    -> incorrect
0x00065bd0 -> CORRECT
65bd0      -> already_solved
0x65BD0    -> already_solved

The grader wants 8 hex digits, zero-padded. The flag from the CORRECT reply was not printed, so it was not recorded.

  1. Fixed the handler to pad to 8 digits:
return '0x%08x' % struct.unpack_from('<I', fb, pe + 0x28)[0]
  1. Time Trial. run_meta.py answered telemetry-agent-002.exe = 0x00063a80. CORRECT.
  2. Mastery. telemetry-agent-003.exe = 0x00063510, telemetry-agent-004.exe = 0x00065bd0. CORRECT.

Results

ModeResultFlag
Single SolveCORRECT? (not recorded)
Time TrialCORRECT76b954ad50ed0880e590fd9176ad6af5
MasteryCORRECT89060b4346e313485c5745d46abeaf27

Reproduce

python3 -I ~/.config/huntress/solvers/run_meta.py metadata-forensics-day-10-where-do-we-begin time_trial /tmp/d10

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 10: Network Config Split

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 split (also used on Day 5).
{"schema":"huntress.mobile.puzzle.v1","day":10,"codec":"split","data":"","parts":["56C4B5B0D","ANS-4","9D8953"],"order":[2,0,1]}
  1. Put the pieces back. order[i] is the output position of parts[i]:
import json
p = json.load(open('single-solve/huntress_puzzle.json'))
out = [None] * len(p['parts'])
for i, pos in enumerate(p['order']):
    out[pos] = p['parts'][i]
print(''.join(out))

Output: ANS-49D895356C4B5B0D.

  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-10-network-config-split <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-49D895356C4B5B0D), Time Trial (ANS-67B16EA61D3B7431) and all three Mastery answers came back CORRECT.

Results

ModeResultFlag
Single SolveCORRECTa06db7733db43449a9a7f52bee56254a
Time TrialCORRECTbdb66dc9cd580f3c220afaee3cf0af82
MasteryCORRECT6d61c888cec1cd994bf7a6244e87a46b

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-10-network-config-split single_solve mobile_puzzle /tmp/d10

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 10: Bind Over Matter

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 the new family. A first survey suggested a separate mof-* family. The question IDs showed the real prefix is polyglot-wmi_mof-*, which the polyglot path already handles. The MOF files carry the usual marker.
  1. Submitted with no code change. The Single Solve was CORRECT (753/753).
  1. Real answers from single-solve/answers.json:
{
 "polyglot-wmi_mof-launcher-role": "launcher",
 "polyglot-wmi_mof-launcher-attack": "T1059",
 "polyglot-wmi_mof-launcher-adapter": "process_builder",
 "polyglot-wmi_mof-launcher-campaign": "WMI_MOF-95703e20",
 "polyglot-wmi_mof-launcher-url": "https://wmi_mof-95703e207f.example.invalid/stage",
 "polyglot-wmi_mof-launcher-stage-count": "2",
 "polyglot-wmi_mof-launcher-steps": "decode_configuration>return_configuration",
 "polyglot-wmi_mof-launcher-host-profile": "standalone"
}
  1. Time Trial and Mastery used the same solver on fresh variants.

Results

ModeResultFlag
Single SolveCORRECT6eb0b0b8838ddba9e0698b971f1a52dd
Time TrialCORRECT3d0b14f52c6cf33d3b8713497fad654a
MasteryCORRECT80b0fe98fcc3ff18d933057e082a366f

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/d10/ex
7z x -pinfected -o/tmp/d10/ex repos/day-10-script-analysis-bind-over-matter/single-solve/evidence.zip
python3 -I tools/solve_expansion.py /tmp/d10/ex \
  repos/day-10-script-analysis-bind-over-matter/single-solve/start-response.json /tmp/d10/answers.json

This rebuilds all 753 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 10: Thirty-Two Below

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. Base32-decode the blob (A-Z, 2-7 alphabet, = padding).
  2. Mastery blobs use multiple encodings from Days 1-10. 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