2026-10-13

Day 13: Crystal Clear

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–d12 were answered as on Day 12.
  3. d13 config: this one is Base64 again (like Day 8 and Day 9). The question said to Base64-decode every run of 100+ Base64 characters and accept the first that decodes to a CRC32-valid HCFG record.

Re-checked on the saved sample:

[base64 run at file offset 560188, run length 508]
HCFG version=1 xor_key=0x91 len=368 crc32=0xa69b7e61
section of match: .rodata
JSON: {"campaign":"BR13-000","domain":"node-000.day13.example.invalid","ipv4":"198.51.100.240","url":"https://node-000.day13.example.invalid/api/BR13-000","mutex":"Global\\HuntressBR13_000", ...}

Answers: format elf, d13_analysis_hcfg_offset = 560188, CRC32 0xa69b7e61, campaign BR13-000.

  1. Same code paths as before: the Base64 scan (Days 8–9) and the lowercase format token (Day 12) handle this specimen.
  2. Submitted all 130 answers (answers.json). Result: CORRECT.
  3. Time Trial: a fresh variant, same steps. Result: CORRECT.
  4. Mastery: five deliveries (650 answers), same steps. Result: CORRECT.

Results

ModeResultFlag
Single SolveCORRECTe90a1d71b26f714fa22ca48d25ffdd81
Time TrialCORRECT19105c22b99fe95b146ac24b65fcbc79
MasteryCORRECTbe2d0e037e64dec9a723f2bcc8a30745

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

Checked on 2026-11-01: this gives the same 130 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-13-crystal-dns-configuration single_solve /tmp/d13

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

Day 13: Product Placement

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

  1. Wrote an MSI reader, msi_product.py (no third-party libraries). An MSI file is an OLE2 compound file with database tables inside:
  2. Parse the OLE2 header: sector size, FAT, DIFAT, mini-FAT and the directory.
  3. Decode the stream names. MSI packs table names into special Unicode ranges (0x3800–0x4840).
  4. Read _StringPool and _StringData to build the string table.
  5. Read the Property table. It has 2 columns stored column by column, and each cell is a string index (2 bytes, or 3 for very large pools).
  6. Return the value in the row whose key is ProductCode.
  7. Single Solve. installer-001.msi → {DD1A80D5-0250-4F4D-B289-13096D633C61}. This is the native form: braces and capitals. CORRECT. Then the reader was added to run_meta.py (product-code → product_property(fb, 'ProductCode')).
  8. Time Trial, first run. It had the new synthesis question, which the driver did not know yet. Mastery also hit an HTTP 409 because other agents were using the Game Master at the same time.
  9. Added the synthesis handler. It reads the file list from the question text, hashes each file and sorts by digest:
q = QTEXT.get(aid, '')                       # question text by answer ID
files = json.loads('[' + re.search(r'\[([^\]]*)\]', q).group(1) + ']')
pairs = sorted((hashlib.sha256(find_file(bundle, n)).hexdigest(), n) for n in files)
return json.dumps([n for _, n in pairs], separators=(',', ':'))

The driver also had to fill QTEXT from the start reply, so the handler can see the question text.

  1. Re-ran the Time Trial and Mastery. Examples:

Both CORRECT.

Results

ModeResultFlag
Single SolveCORRECT08f8cae6e366a7ce09136c4c624594d5
Time TrialCORRECTc63c8204795f6b769fd65ae5a3ed4764
MasteryCORRECT26d7b8df8df6c48e76403ddc961691cf

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/msi_product.py installer-001.msi ProductCode
python3 -I ~/.config/huntress/solvers/run_meta.py metadata-forensics-day-13-product-placement single_solve /tmp/d13

The first line only needs the extracted .msi. The second 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. Nothing here installs or runs the MSI.

Day 13: Keystore Misuse

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 base64.
{"schema":"huntress.mobile.puzzle.v1","day":13,"codec":"base64","data":"QU5TLTc3Mzc2MkU4NTc5NzA2NEM="}
  1. Decoded it:
import json, base64
p = json.load(open('single-solve/huntress_puzzle.json'))
print(base64.b64decode(p['data']).decode())

Output: ANS-773762E85797064C.

  1. Ran the lane driver for all three modes:
python3 -I ~/.config/huntress/solvers/run_mode.py mobile-android-day-13-keystore-misuse <mode> mobile_puzzle <workdir>

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

  1. Results: Single Solve (ANS-773762E85797064C), Time Trial (ANS-D5B50F331B9FF35F) and all five Mastery answers came back CORRECT.

Results

ModeResultFlag
Single SolveCORRECTf26064b81339f0d01a757e87d6e110ba
Time TrialCORRECT3aee54eed12b7e86f98828ae4605f1a9
MasteryCORRECTaf95b5bc49ea89bd0eb55463f26e5a34

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-13-keystore-misuse single_solve mobile_puzzle /tmp/d13

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 13: Zip Code

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 prompt talks about nested containers, but every question points at a file at the top of evidence.zip (for example evidence.zip -> array-slicing.sh). A normal 7z extract found every file.
  1. Ran run_expansion.py for all three modes in one loop. All three came back CORRECT.
  1. Real answers from single-solve/answers.json:
{
 "polyglot-applescript-downloader-role": "downloader",
 "polyglot-applescript-downloader-attack": "T1105",
 "polyglot-applescript-downloader-adapter": "http_client",
 "polyglot-applescript-downloader-campaign": "APPLESCRIPT-a810b5b7",
 "polyglot-applescript-downloader-url": "https://applescript-a810b5b73c.example.invalid/stage",
 "polyglot-applescript-downloader-stage-count": "3",
 "polyglot-applescript-downloader-steps": "decode_embedded>write_file>dispatch_process",
 "polyglot-applescript-downloader-host-profile": "standalone"
}
  1. Time Trial and Mastery used the same solver on fresh variants.

Results

ModeResultFlag
Single SolveCORRECTb93ebbecd3882cec00667c7166a5b967
Time TrialCORRECT60bf2b5e7109969e83ec4e4c0745e8ad
MasteryCORRECTab97797d67c83aac1406317a40f5a7f2

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/d13/ex
7z x -pinfected -o/tmp/d13/ex evidence.zip
python3 -I tools/solve_expansion.py /tmp/d13/ex start-response.json /tmp/d13/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 13: Opposite Day

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. Letter substitution: A maps to Z, B to Y, and so on. Apply the same mapping to decode.
  2. Mastery blobs use multiple encodings from Days 1-13. 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