2026-10-10
Day 10: Zig Zag
Lane: Binary reverse engineering. Modes: Single Solve, Time Trial, Mastery. Result: all CORRECT.
The challenge
- ID:
binary-reverse-engineering-day-10-zig-cross-platform-services - Prompt: "Zig promises one binary for every platform. Compare the ELF and PE service descriptors side by side and prove they're the same program wearing different uniforms."
What we were given
- One
evidence.zip(31,546,122 bytes, SHA-2569c31fb3a95b866cc9984b7db740db1a36e9f59fc7ecb924f8dc497cae2b11fc4). AES encrypted, passwordinfected. - The earlier files again:
d01tod09. - New today:
d10, a program written in Zig. It comes as an ELF or a PE: - Single Solve and Time Trial:
d10--variant-000.elf(134,720 bytes in Single Solve), a Linux ELF. - Mastery sets 2 and 3: a Windows PE32+ build instead.
What was asked
- 100 questions in Single Solve and Time Trial. Mastery had three deliveries, so 300.
- Question types:
- Hashes: SHA-256 of each member.
- d01 to d09: the same questions as Day 9.
- d10 (new): machine, format, architecture, the config fields, the CRC32, and a new yes/no field:
has_hcfg_section, true when any section name contains the lowercase texthcfg.
How it was solved, start to finish
- Ran the driver
run_tm.py: start the attempt, download the zip, runsolve_tm.py, submit. - d01–d09 were answered as on Day 9.
- d10 config: the question said to scan the file for literal
HCFGand accept the first valid record.
- The old note for this day said the config came from a Base64 run. On the saved Single Solve sample it is a plain record inside a section named
.hcfg. solve_tm.pytries a literal record first and Base64 runs second, so either layout is covered.
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", ...}
- d10 section check (new): added
has_hcfg_sectiontosolve_tm.py:
- For an ELF, look through the section names.
- For a PE, read the 8-byte names from the PE section table.
- Answer
trueif any name containshcfg. Here it wastrue(the.hcfgsection).
- Submitted all 100 answers (
answers.json). Examples:d10_analysis_has_hcfg_section=true,d10_analysis_config_crc32_hex=0xceda03ad. Result:CORRECT. - Time Trial: a fresh variant (campaign
BR10-007), same steps. Result:CORRECT. - Mastery: three deliveries (300 answers). Sets 2 and 3 had the PE build of d10 (campaigns
BR10-001andBR10-006). The format and machine code reads ELF and PE headers alike, so the same steps worked. Result:CORRECT.
Results
| Mode | Result | Flag |
|---|---|---|
| Single Solve | CORRECT | d78c629de45c9048c1a19b904fcf4d97 |
| Time Trial | CORRECT | 1bd84a8a046cfcd0cc66288022efea17 |
| Mastery | CORRECT | c6e1925c9b17409c5f7d68d7ab26ae12 |
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
- ID:
metadata-forensics-day-10-where-do-we-begin - Prompt: "Architecture tells you whether a binary can run; its entry point tells you where execution begins. Map the start addresses and catch the report that is lying."
What we were given
- Single Solve:
(evidence.zipmetadata-day-10-evidence.zip, 595,471 bytes, SHA-25675db7f473673d7f55503920cbcd4a9945b44e3a9705c4cd62248975469ea3407) withtelemetry-agent-001.exe. - Time Trial:
metadata-day-10-evidence.zip(611,883 bytes, SHA-25672336cea74300ed7eec912b887793ae517fdf8250fc4d485ce4cf68b105adca9) withtelemetry-agent-002.exe. - Mastery:
metadata-forensics-day-10-where-do-we-begin-mastery.zip(1,166,796 bytes, SHA-256097bb491253ea35ad3fd3c6603a9095c2470a5439b8fc3d8bba1e248317d72ea). Two inner zips:metadata-day-10-evidence-01.zip(telemetry-agent-003.exe) and-02.zip(telemetry-agent-004.exe).
What was asked
- One field type:
pe.address_of_entry_point_rva_hex, the entry point address (RVA) of a Windows PE file. - The answer ID reuses the Day 9 prefix:
d09-pe-001-pe-address-of-entry-point-rva-hex. - Format text: "lowercase hexadecimal with a 0x prefix and no explanatory text". It does not mention padding, but padding matters (see step 3).
- Single Solve and Time Trial: 1 question. Mastery: 2 questions (
set1.,set2.). Timers: Time Trial 50 seconds, Mastery 80 seconds.
How it was solved, start to finish
- Added a handler to
run_meta.py.AddressOfEntryPointis 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
- 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
0x65bd0fortelemetry-agent-001.exe. The Game Master saidincorrect. That reply is the one saved insubmit-response.json. - 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.
- Fixed the handler to pad to 8 digits:
return '0x%08x' % struct.unpack_from('<I', fb, pe + 0x28)[0]
- Time Trial.
run_meta.pyansweredtelemetry-agent-002.exe=0x00063a80.CORRECT. - Mastery.
telemetry-agent-003.exe=0x00063510,telemetry-agent-004.exe=0x00065bd0.CORRECT.
Results
| Mode | Result | Flag |
|---|---|---|
| Single Solve | CORRECT | ? (not recorded) |
| Time Trial | CORRECT | 76b954ad50ed0880e590fd9176ad6af5 |
| Mastery | CORRECT | 89060b4346e313485c5745d46abeaf27 |
- Each mode folder has
answers.json,start-response.json,submit-response.jsonandfinal-status-response.json. - The Single Solve files are from the unpadded run (
0x65bd0,incorrect). TheCORRECTpadded submit was a one-off test and its reply was not saved. - No screenshots were captured.
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
- ID:
mobile-android-day-10-network-config-split - Prompt: "Diff manifest and Network Security Config variants to locate the true transport exception."
What we were given
- One Android APK per case. Today's APK is a bit bigger (12,845 bytes). Besides
AndroidManifest.xml,classes.dexandassets/huntress_puzzle.json, it addsres/xml/network_security_config.xmlandresources.arsc. - Single Solve:
network_config_split.apk, caseMOB-10-A4B83C4513, SHA-256c4a967db659bb471bbd939b41eb97baf96e7bc8c10f8deaed0e9927522ce3a59. Its puzzle is saved assingle-solve/huntress_puzzle.json. - Time Trial: one APK (case
MOB-10-496B9A4C07). Mastery: three 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.answertoset3.answerfor Mastery. - Time limits: Time Trial 50 seconds, Mastery 110 seconds.
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
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]}
- Put the pieces back.
order[i]is the output position ofparts[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.
- 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.
- Results: Single Solve (
ANS-49D895356C4B5B0D), Time Trial (ANS-67B16EA61D3B7431) and all three Mastery answers came backCORRECT.
Results
| Mode | Result | Flag |
|---|---|---|
| Single Solve | CORRECT | a06db7733db43449a9a7f52bee56254a |
| Time Trial | CORRECT | bdb66dc9cd580f3c220afaee3cf0af82 |
| Mastery | CORRECT | 6d61c888cec1cd994bf7a6244e87a46b |
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
- ID:
script-analysis-day-10-wmi-persistence-reconstruction - Prompt: "A MOF file declares classes, namespaces, filters, and consumers, but only some bindings actually tie them together. Reconstruct the persistence intent, separate the operational relationships from the decoys, and name the subscription that would really survive a reboot."
What we were given
- One
evidence.zip(85,552 bytes, SHA-256c21e43b382a0cc1a6082dc7d241bcd66a11b995e7f983ae3e62a397af756d475). Password:infected. - The same families as Day 9. New today:
- 4 WMI MOF polyglots:
polyglot-wmi_mof-benign-utility.mof,-downloader,-launcher,-staged-chain. - 2 more advanced Bash files:
here-string.sh,heredoc-reconstruction.sh. - Every host and polyglot file carries the
HUNTRESS_ANALYSIS_V1:<ENC>-<data>marker fromDay 8.
What was asked
- 753 questions in Single Solve. By family: PowerShell 15, JScript 72, Batch 72, VBScript 72, Python 126, Bash 98, Node.js 56, host 66, polyglot 176.
- 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: 753 questions. Mastery: 1,506 questions in 2 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.
- Checked the new family. A first survey suggested a separate
mof-*family. The question IDs showed the real prefix ispolyglot-wmi_mof-*, which the polyglot path already handles. The MOF files carry the usual marker.
- Submitted with no code change. The Single Solve was
CORRECT(753/753).
- 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"
}
- Time Trial and Mastery used the same solver on fresh variants.
- Time Trial: 753 questions, deadline 50 seconds after the start.
- Mastery: 1,506 questions in 2 sets, deadline 80 seconds after the start. The download (
script-analysis-day-10-wmi-persistence-reconstruction-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 | 6eb0b0b8838ddba9e0698b971f1a52dd |
| Time Trial | CORRECT | 3d0b14f52c6cf33d3b8713497fad654a |
| Mastery | CORRECT | 80b0fe98fcc3ff18d933057e082a366f |
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
- ID:
warmups-day-10 - Prompt: "With thirty-two symbols and just a little padding, you can say anything."
- New encoding: base32
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. Base32-decode the blob (A-Z, 2-7 alphabet,
=padding). - 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. - 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:groovy-starfish-willow-93. Flag:2b660ea4d1ebdcedd163f6fee9155d90. - Time Trial:
CORRECT. slug:plucky-valley-clover-80. Flag:1cf643210773894b1b4ec041863f0366. - Mastery:
CORRECT. 48 slugs. Flag:2fd4f92fac7b8131f816ae67270991d9.