2026-10-16
Day 16: Wasm Up
Lane: Binary reverse engineering. Modes: Single Solve, Time Trial, Mastery. Result: all CORRECT.
The challenge
- ID:
binary-reverse-engineering-day-16-webassembly-optimization-equivalence - Prompt: "WebAssembly runs in a sandbox, but the sandbox has doors: imports, memory, indirect calls. Map every door in this module and inventory what passes through."
What we were given
- One
evidence.zip(32,253,202 bytes, SHA-2564db4b6fb39470e118624e3ee1aba915578146020b158f4c74a174abace35aa1d). AES encrypted, passwordinfected. - The earlier files again:
d01tod15. - New today: two small WebAssembly modules (magic bytes
\0asm): d16--variant-000-direct.wasm(570 bytes)d16--variant-000-compact.wasm(561 bytes)
What was asked
- 160 questions in Single Solve and Time Trial. Mastery had five deliveries, so 800.
- Question types:
- Hashes: SHA-256 of each member.
- d01 to d15: the same questions as Day 15.
- d16 (new): for each module (
compact_…/direct_…): architecture (x86-64orwasm32) and format (lowercase token). Plus the config fieldscampaign,domain,mutexandurlfrom the compact module.
How it was solved, start to finish
- Ran the driver
run_tm.py: start the attempt, download the zip, runsolve_tm.py, submit. - d01–d15 were answered as on Day 15.
- Pick the right module: the Day 15 selector also covers
compactanddirect. The solver uses the member whose name contains that word. - WebAssembly support (new):
solve_tm.pynow treats a file that starts with\0asmas WebAssembly:
- Format token
wasm. - Architecture
wasm32(a module has no CPU machine field).
- d16 config: the question said to walk the WebAssembly sections and look in the data section payload for a literal, CRC32-valid
HCFGrecord. The plainHCFGscan 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", ...}
- Answers for d16: both formats
wasm, both architectureswasm32,compact_config_campaign=BR16-000. - Submitted all 160 answers (
answers.json). Result:CORRECT. - Time Trial: a fresh variant, same steps. Result:
CORRECT. - Mastery: five deliveries (800 answers), same steps. Result:
CORRECT.
Results
| Mode | Result | Flag |
|---|---|---|
| Single Solve | CORRECT | c664d2d2d78d7ab6811df6001cb7803b |
| Time Trial | CORRECT | ac778c0b4141701da85a0a233900f0b5 |
| Mastery | CORRECT | 4c6bf5fa2b84ca0faeed31976cef0d5d |
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
- ID:
metadata-forensics-day-16-return-to-sender - Prompt: "A mailbox export contains replies, forwards, duplicates, and reconstructed messages. Use stable message identities to rebuild which mail actually belongs together."
What we were given
- Single Solve:
(evidence.zipmetadata-day-16-evidence.zip, 602 bytes) withmessage-001.eml. - Time Trial:
evidence.zip(606,873 bytes, SHA-256e200bc5970169055842b7c4c4398d2f0945e3009ee73a43b764cf1e01a2e7f6d). One file of each type so far, now includingmessage-001.eml. - Mastery:
metadata-forensics-day-16-return-to-sender-mastery.zip(3,034,833 bytes, SHA-2569d387e8883ba4003db98f86a6ff7451e7298dbd145465a218d093ce576d52332). Five inner zips,evidence-01.ziptoevidence-05.zip. - New today: email files (
.eml).
What was asked
- Single Solve: 1 question:
email.message_idformessage-001.eml. Format: the exact value, no quotes or extra text. - Time Trial: 21 questions. Mastery: 105 (5 sets × 21).
- Question types: everything from Day 15, plus the new email
Message-ID.
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.
- Read the header in the Single Solve file. The value is
<artifact-assembly-line@example.test>, angle brackets included. - 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
- Single Solve. Submitted
<artifact-assembly-line@example.test>.CORRECT. - Time Trial and Mastery. After the new handlers for the day were tested, all lanes were run by helper agents.
run_meta.pyanswered all 21 and all 105. TheMessage-IDwas<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"]. BothCORRECT.
Results
| Mode | Result | Flag |
|---|---|---|
| Single Solve | CORRECT | 1d4d575ab8ceff294b9caef287a9ad6c |
| Time Trial | CORRECT | f5e0aef77352c3306aa34368b7ba9cb4 |
| Mastery | CORRECT | c936d49713665e3363e6f36519f18adb |
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
- ID:
mobile-android-day-16-jni-boundary - Prompt: "Identify a Java-to-native type or length assumption that changes backend authorization."
What we were given
- One Android APK per case. Like Day 15, it carries a native library,
lib/x86_64/libarena.so. The APK is 12,772 bytes. - Single Solve:
jni_boundary.apk, caseMOB-16-6B50835383, SHA-256f5de03f0e210775b53387632d2e409b6d3740c815e5d11ef72646d47e2067164. Its puzzle is saved assingle-solve/huntress_puzzle.json. - Time Trial: one APK (case
MOB-16-17BC8D6B07). Mastery: five APKs. These APKs were not saved in the repo.
What was asked
- One question per case: return the exact backend answer code for that case.
- Answer format:
ANS-plus exactly 16 uppercase hex characters. - Answer IDs:
answerfor Single Solve and Time Trial.set1.answertoset5.answerfor Mastery. - Mastery mixed cases from Days 1, 4, 11, 13 and 16.
How it was solved, start to finish
The app was never installed or run.
- Started the Single Solve and downloaded the APK.
- Read the puzzle asset. The codec is
nativeagain, with the answer inline:
{"schema":"huntress.mobile.puzzle.v1","day":16,"codec":"native","data":"ANS-901682D7DCA93404"}
- No new decoder was needed. Since Day 15 the driver returns
dataas is fornative. - 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.
- Results: Single Solve (
ANS-901682D7DCA93404), Time Trial (ANS-B715EE9DE5149245) and all five Mastery answers came backCORRECT.
Results
| Mode | Result | Flag |
|---|---|---|
| Single Solve | CORRECT | d4b04b9749555c799b192ce66213b7ed |
| Time Trial | CORRECT | 815aef9cbb47e8bf8e37ecdff3fea80e |
| Mastery | CORRECT | b07268c07b7becf04bfaa4631fded1bb |
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
- ID:
script-analysis-day-16-obfuscation-equivalence - Prompt: "Several obfuscation families have scrambled the same logic independently, or so they claim. Strip each version down to its semantics, prove which ones are truly equivalent, and expose the variant that quietly changed the plot."
What we were given
- One
evidence.zip(113,162 bytes, SHA-256be61ff1436f7c9ed9036ecf2623877472086c08cae4dc86faed91dab9ae31c76). Password:infected. - The same families as Day 15. New today:
- 1 new host file:
host-ruby-rack-ruby.rb(Ruby Rack). - 4 Ruby polyglots:
polyglot-ruby-benign-utility.rb,-downloader,-launcher,-staged-chain. - 2 more advanced Bash files:
ansi-c-quoting.sh,regex-conditional.sh. - Every host and polyglot file carries the
HUNTRESS_ANALYSIS_V1:<ENC>-<data>marker fromDay 8.
What was asked
- 1,095 questions in Single Solve. By family: PowerShell 15, JScript 72, Batch 72, VBScript 72, Python 126, Bash 154, Node.js 56, host 88, polyglot 440.
- The question types are the same as before. Host and polyglot files get 11 questions each (role, ATT&CK, adapter, campaign, URL or path, host profile, obfuscation, stage profile, next language, stage count, steps).
- Time Trial: 1,095 questions. Mastery: 5,475 questions in 5 sets.
How it was solved, start to finish
- Started the untimed Single Solve and downloaded
evidence.zip. Extracted it with7z x -pinfected. - Ran the existing solver (
solve_expansion.py, driven byrun_expansion.py). Each family has its own decoder:
| Family | Files | How the config is recovered | First seen | |
|---|---|---|---|---|
| PowerShell | *-sample.ps1 | Base64 JSON inside FromBase64String('...') | Day 1 | |
| JScript | *.js | jsdec.js loads the fixture in a Node vm sandbox (pure-computation globals only) and calls its decode functions | Day 3 | |
| Batch | *.bat, *.cmd | joins the :HUNTRESS_INSPECT fragments and drops ^ carets | Day 3 | |
| VBScript | *.vbs | Material_ + Codec_, transform search until the text starts `v=1\ | steps=` | Day 4 |
| Python | *.py | MATERIAL_ read with ast.literal_eval, same transform search | Day 5 | |
| Bash | *.sh | quoted Material_ + Codec_; "advanced" files start `v=1\ | feature=` | Day 6, Day 7 |
| Node.js | node-*.mjs | Material_ + Codec_ with \x, \u and hex-array formats | Day 7 | |
| host, polyglot | host-*, 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.
- No new code was needed. The Ruby files carry the usual marker.
- 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
CORRECTin all three modes.
- 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"
}
- Time Trial and Mastery used the same solver on fresh variants.
- Time Trial: 1,095 questions, no deadline (
run_for_time: false). - Mastery: 5,475 questions in 5 sets, no deadline (
run_for_time: false). The download (script-analysis-day-16-obfuscation-equivalence-mastery.zip) holds one inner zip per set. The driver solves each set and adds thesetN.prefix. - Both came back
CORRECT.
Results
| Mode | Result | Flag |
|---|---|---|
| Single Solve | CORRECT | 051b4cece167dd8cf431c32639395c5b |
| Time Trial | CORRECT | a8109dc30859fe9d7e57f5e48e345384 |
| Mastery | CORRECT | daf96359cb697f47239eb81677065de0 |
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
- ID:
warmups-day-16 - Prompt: "Sixteen little symbols are calling. Dot dot dot."
- New encoding: Morse code to hex to ASCII
What we were given
- One blob file per mode (Single Solve and Time Trial), or a zip of multiple blobs (Mastery).
- Each blob has numbered lines (
NN<TAB>fragment). Each line is independently encoded. - The decoded text ends with a slug like
word-word-word-NNto submit.
How it was solved
- Decode the blob. Dots-and-dashes tokens decode to hex characters via standard Morse, then hex-decode the result to ASCII.
- 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. - Concatenate all decoded lines. The text contains a message ending in the answer slug.
- Submit the slug to the Game Master.
Results
- Single Solve:
CORRECT. slug:silly-banner-marble-88. Flag:407dd86d6cbe6ef01ca3668bdde02249. - Time Trial:
CORRECT. slug:daring-castle-hazel-90. Flag:9b012dbf573bf8e3528832378a22152d. - Mastery:
CORRECT. 78 slugs. Flag:09740de118a0baa89ee956f2d8777fed.