2026-10-16

Day 16: Wasm Up

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–d15 were answered as on Day 15.
  3. Pick the right module: the Day 15 selector also covers compact and direct. The solver uses the member whose name contains that word.
  4. WebAssembly support (new): solve_tm.py now treats a file that starts with \0asm as WebAssembly:
  1. d16 config: the question said to walk the WebAssembly sections and look in the data section payload for a literal, CRC32-valid HCFG record. The plain HCFG scan finds it. Re-checked on the saved samples (section 11 is the data section):
compact.wasm  sections (id, start, size): (1,14,6) (3,26,2) (5,34,3) (7,43,21) (10,70,32) (11,108,453)
              HCFG at offset 116, inside section 11
direct.wasm   sections (id, start, size): (1,14,6) (3,26,2) (5,34,3) (7,43,21) (10,70,41) (11,117,453)
              HCFG at offset 125, inside section 11
both: version=1 xor_key=0xc1 len=367 crc32=0xf6cf27e5
JSON: {"campaign":"BR16-000","domain":"node-000.day16.example.invalid","ipv4":"198.51.100.60","url":"https://node-000.day16.example.invalid/api/BR16-000","mutex":"Global\\HuntressBR16_000", ...}
  1. Answers for d16: both formats wasm, both architectures wasm32, compact_config_campaign = BR16-000.
  2. Submitted all 160 answers (answers.json). Result: CORRECT.
  3. Time Trial: a fresh variant, same steps. Result: CORRECT.
  4. Mastery: five deliveries (800 answers), same steps. Result: CORRECT.

Results

ModeResultFlag
Single SolveCORRECTc664d2d2d78d7ab6811df6001cb7803b
Time TrialCORRECTac778c0b4141701da85a0a233900f0b5
MasteryCORRECT4c6bf5fa2b84ca0faeed31976cef0d5d

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

Checked on 2026-11-01: this gives the same 160 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-16-webassembly-optimization-equivalence single_solve /tmp/d16

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

Day 16: Return to Sender

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: every email has a Message-ID: header. Copies of the same mail keep it, so it works as a stable identity.

  1. Read the header in the Single Solve file. The value is <artifact-assembly-line@example.test>, angle brackets included.
  2. Added a handler to run_meta.py. It finds the header line, case-insensitive, and keeps the value as written:
m = re.search(rb'(?im)^Message-ID:[ \t]*(.+?)[ \t\r]*$', fb)
return m.group(1).decode('utf-8', 'replace').strip() if m else None
  1. Single Solve. Submitted <artifact-assembly-line@example.test>. CORRECT.
  2. Time Trial and Mastery. After the new handlers for the day were tested, all lanes were run by helper agents. run_meta.py answered all 21 and all 105. The Message-ID was <artifact-assembly-line@example.test> in every set. Example synthesis answer (Time Trial): ["message-001.eml","evidence-note.txt","managed-001.dll","panel-001.png"]. Both CORRECT.

Results

ModeResultFlag
Single SolveCORRECT1d4d575ab8ceff294b9caef287a9ad6c
Time TrialCORRECTf5e0aef77352c3306aa34368b7ba9cb4
MasteryCORRECTc936d49713665e3363e6f36519f18adb

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

python3 -I ~/.config/huntress/solvers/run_meta.py metadata-forensics-day-16-return-to-sender single_solve /tmp/d16

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 only reads the mail headers.

Day 16: JNI Boundary

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 native again, with the answer inline:
{"schema":"huntress.mobile.puzzle.v1","day":16,"codec":"native","data":"ANS-901682D7DCA93404"}
  1. No new decoder was needed. Since Day 15 the driver returns data as is for native.
  2. Ran the lane driver for all three modes:
python3 -I ~/.config/huntress/solvers/run_mode.py mobile-android-day-16-jni-boundary <mode> mobile_puzzle <workdir>

The driver picks the decoder from each APK's own codec field, so the mixed Mastery set works the same way.

  1. Results: Single Solve (ANS-901682D7DCA93404), Time Trial (ANS-B715EE9DE5149245) and all five Mastery answers came back CORRECT.

Results

ModeResultFlag
Single SolveCORRECTd4b04b9749555c799b192ce66213b7ed
Time TrialCORRECT815aef9cbb47e8bf8e37ecdff3fea80e
MasteryCORRECTb07268c07b7becf04bfaa4631fded1bb

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

Reproduce

Offline:

unzip -p single-solve/jni_boundary.apk assets/huntress_puzzle.json

A fresh run with the driver:

python3 -I ~/.config/huntress/solvers/run_mode.py mobile-android-day-16-jni-boundary single_solve mobile_puzzle /tmp/d16

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 16: Same Same, But Different

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 Ruby files carry the usual marker.
  1. Ran all three modes. By this day every lane's solver was ready, so all five file lanes ran as parallel agents. The script lane came back CORRECT in all three modes.
  1. Real answers from single-solve/answers.json:
{
 "host-ruby-rack-ruby-role": "staged_chain",
 "host-ruby-rack-ruby-attack": "T1059",
 "host-ruby-rack-ruby-adapter": "operation_graph",
 "host-ruby-rack-ruby-campaign": "RUBY-dd072008",
 "host-ruby-rack-ruby-url": "https://ruby-dd07200803.example.invalid/stage",
 "host-ruby-rack-ruby-stage-count": "2",
 "host-ruby-rack-ruby-steps": "acquire_remote>dispatch_process",
 "host-ruby-rack-ruby-host-profile": "ruby_rack"
}
  1. Time Trial and Mastery used the same solver on fresh variants.

Results

ModeResultFlag
Single SolveCORRECT051b4cece167dd8cf431c32639395c5b
Time TrialCORRECTa8109dc30859fe9d7e57f5e48e345384
MasteryCORRECTdaf96359cb697f47239eb81677065de0

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/d16/ex
7z x -pinfected -o/tmp/d16/ex evidence.zip
python3 -I tools/solve_expansion.py /tmp/d16/ex start-response.json /tmp/d16/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 16: Dot Com

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. Dots-and-dashes tokens decode to hex characters via standard Morse, then hex-decode the result to ASCII.
  2. Mastery blobs use multiple encodings from Days 1-16. 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