2026-10-05

Day 5: Rust Belt

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. Routine fields for d01–d04 were answered exactly as on Day 4.
  3. d05 (the new part): the question said to scan each literal HCFG in the Rust file and accept the first record whose bounds, CRC32 and JSON all check out.

Re-checked on the saved sample:

HCFG offset=355376 version=1 xor_key=0x61 len=368 crc32=0x8f37c323
section of match: .rodata
JSON: {"campaign":"BR05-000","domain":"node-000.day05.example.invalid","ipv4":"198.51.100.100","url":"https://node-000.day05.example.invalid/api/BR05-000","mutex":"Global\\HuntressBR05_000", ...}

Answers: format ELF64, architecture x86-64, CRC32 0x8f37c323, campaign BR05-000.

  1. Submitted all 40 answers (answers.json). Result: CORRECT.
  2. Time Trial: a fresh variant, same steps. Result: CORRECT.
  3. Mastery: two deliveries (80 answers), same steps. Result: CORRECT.

Results

ModeResultFlag
Single SolveCORRECT12b9e4c1568b8fa4333f754d39ba4961
Time TrialCORRECT26e9642973f65fd86ae75be16cbf70f9
MasteryCORRECTb0157461375296677b36d1253ffaae91

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

Checked on 2026-11-01: this gives the same 40 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-05-rust-runtime-shapes single_solve /tmp/d05

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

Day 5: Chunk Norris

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: read the true size from the PNG IHDR chunk, not from how the image looks.

  1. Single Solve. Downloaded the zip and extracted panel-001.png. A PNG starts with an 8-byte signature. The first chunk is IHDR. Its data starts at byte 16: width (4 bytes) then height (4 bytes), both big-endian.
def png_ihdr(b):
    assert b[:8] == b'\x89PNG\r\n\x1a\n'
    w, h = struct.unpack('>II', b[16:24])
    return '%dx%d' % (w, h)

Result: 269x153. Submitted as d05-png-001-png-ihdr-dimensions-pixels. CORRECT.

  1. Added png_ihdr to the driver run_mode.py (built on Day 4) and ran the Time Trial. Answer for panel-002.png: 282x162. CORRECT.
  2. Mastery, first try failed. The bundle was nested (outer zip → evidence-0N.zip → panel-XXX.png) and the driver did not look inside the inner zips.
  3. Fixed the driver. It now extracts with 7z x -y -pinfected (plain or AES zips) and searches the zip tree, up to 4 levels deep, for the file named in the question (find_file).
  4. Mastery, after the fix. Answers: panel-006.png = 334x198, panel-007.png = 347x207. CORRECT.

Results

ModeResultFlag
Single SolveCORRECTc6b8d0a1587b0a922cad26398bfc87f6
Time TrialCORRECTbdb56dcda63cbfa01f89ceaafed3d074
MasteryCORRECTd97d8a80e66afc8ecd63f5539c7c1bea

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 and the PNG; 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_mode.py metadata-forensics-day-05-chunk-norris single_solve png_ihdr /tmp/d05

This needs a Game Master token in ~/.config/huntress/gm-token. For time_trial and mastery the driver calls op=retry first, which spends one of the unique attempts. It only parses the image bytes.

Day 5: Backup Spill

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. New codec today: split. The code is cut into pieces and shuffled.
{"schema":"huntress.mobile.puzzle.v1","day":5,"codec":"split","data":"","parts":["0A353BE7B","ANS-5","709E18"],"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-5709E180A353BE7B.

  1. Submitted it under answer. The Game Master replied CORRECT.
  2. Taught the driver. Added the same split logic to mobile_puzzle() in run_mode.py.
  3. Time Trial and Mastery: ran run_mode.py on both. Both came back CORRECT.

Results

ModeResultFlag
Single SolveCORRECT33a15ffa668ec78e55c99f54d9d94e20
Time TrialCORRECT04d7174f5a3dd173a29381dabd1b116f
MasteryCORRECT8bbc56e16286fca39182c6887d299501

Each mode folder has answers.json, start-response.json, submit-response.json and final-status-response.json. The Single Solve submit-response.json says already_solved because it is a resubmit. Its final-status-response.json holds the CORRECT result and flag. 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-05-backup-spill single_solve mobile_puzzle /tmp/d05

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 5: Hatch Careful

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 the archive.
  2. Reused solve_expansion.py for the 231 Day 4 questions.
  3. Wrote a Python decoder (pydec.py):
for node in ast.walk(ast.parse(source)):
    if isinstance(node, ast.Assign):
        for t in node.targets:
            if isinstance(t, ast.Name) and t.id.startswith('MATERIAL_'):
                material = ast.literal_eval(node.value)   # data only, nothing runs

Example: pyinstaller-onefile-recovered.py is hex_colon + single_byte_xor and decodes to:

v=2|steps=acquire_remote,write_file|adapter=http_client_to_path|stage_count=1|syntax=generator_pipeline|obfuscation=fstring_fragments|carrier=pyinstaller_onefile|windows_chain=mshta_to_python|campaign_id=campaign-60cc9d6d2f|url=https://60cc9d6d2f.example.invalid/93aeb91b.py|user_agent=HuntressPython
  1. Carrier, Windows chain, syntax and obfuscation are fields in the decoded config, so they were copied as-is.
  2. Role from steps. Python's Command and Scripting Interpreter ID is T1059.006. One URL-safe Base64 file failed at first, and the decoder was fixed for it.
  3. Checked with the partial-submit oracle (see Day 3). Only python:role (14 answers) was rejected. Trying each role value showed the cause: the two relay files want relay, not staged_chain. After that fix the Single Solve was CORRECT.
FileCarrierRole
source-context.pyraw_sourcebenign_utility
pyarmor-source-recovered.pypyarmor_obfuscatedstager
wheel-recovered.pywheel_archivestager
pyinstaller-onefile-recovered.pypyinstaller_onefiledownloader
pyinstaller-onedir-recovered.pypyinstaller_onediruploader
pyc38-recovered.pyhash_based_pyc_38dropper
cxfreeze-msi-recovered.pycx_freeze_msidropper
cxfreeze-recovered.pycx_freeze_executableimpact
current-pyc-recovered.pyhash_based_pyc_currentlauncher
py2exe-console-recovered.pypy2exe_consolelauncher
py2exe-service-recovered.pypy2exe_windows_servicestaged_chain
pyarmor-pyinstaller-recovered.pypyarmor_pyinstallerstaged_chain
embedded-runtime-recovered.pyembeddable_python_runtimerelay
zipapp-recovered.pyzipapp_pyzrelay
  1. Time Trial and Mastery first failed inside the driver, for two reasons:

After both fixes, the Time Trial (50-second deadline) and Mastery (714 questions in two sets, 80-second deadline) both came back CORRECT.

Results

ModeResultFlag
Single SolveCORRECT4c0dc263e3563c73cb37d6fe2a38b002
Time TrialCORRECTff6fe6d53dd879aee6c5ba0e19701844
MasteryCORRECT320bf533e8a436d37652ee605c580d24

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/d05/ex
7z x -pinfected -o/tmp/d05/ex repos/day-05-script-analysis-hatch-careful/single-solve/evidence.zip
python3 -I tools/solve_expansion.py /tmp/d05/ex \
  repos/day-05-script-analysis-hatch-careful/single-solve/start-response.json /tmp/d05/answers.json

This rebuilds all 357 saved answers (re-checked on 2026-11-01). It only parses the files.

Live: python3 -I ~/.config/huntress/solvers/run_expansion.py script-analysis-day-05-python-carrier-lab <mode> <workdir>. This needs a Game Master token. The solvers/ copy runs JScript fixtures in a Node vm sandbox; the tools/ copy does not.

Day 5: By the Numbers

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. Space-separated decimal numbers. Each number is an ASCII code point; convert to its character.
  2. Mastery blobs use multiple encodings from Days 1-5. 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