2026-10-07

Day 7: Routine Check

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–d06 were answered as before.
  3. d07 (the new part): the Kotlin JAR hides its config the same way as the Day 6 Java JAR. The question gave the same recipe:
  4. Open the Main-Class class file and walk its constant pool.
  5. Base64-decode each UTF-8 constant of 80+ Base64 characters.
  6. Accept the first result that is a CRC32-valid HCFG record, then XOR-decode and parse the JSON.

The Day 6 code path handles it. Re-checked on the saved sample:

[jar:Day07Variant000.class base64 run at file offset 206, run length 508]
HCFG version=1 xor_key=0x31 len=368 crc32=0xcf3ea232
JSON: {"campaign":"BR07-000","domain":"node-000.day07.example.invalid","ipv4":"198.51.100.140","url":"https://node-000.day07.example.invalid/api/BR07-000","mutex":"Global\\HuntressBR07_000", ...}

Answers: format Java archive, CRC32 0xcf3ea232, HCFG version 1, campaign BR07-000.

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

Results

ModeResultFlag
Single SolveCORRECTc0813d767b25aadd8074e4cdfefcc5b7
Time TrialCORRECTfa77af724f2534548b9785781f5f1de0
MasteryCORRECT8a588fb8b39eb0072baabcc20929759d

Each mode folder has the raw start-response.json, answers.json, submit-response.json and final-status-response.json.

Notes on the saved files:

Reproduce

Offline, from this folder (no Game Master needed):

mkdir -p /tmp/d07/deliveries && cp single-solve/evidence.zip /tmp/d07/deliveries/delivery-1.zip
python3 -I ~/.config/huntress/solvers/solve_tm.py single-solve/start-response.json /tmp/d07/deliveries /tmp/d07/answers.json

Checked on 2026-11-01: this gives the same 56 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-07-kotlin-staging-logic single_solve /tmp/d07

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

Day 7: Seven-Zip, No Relation

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. Single Solve, by hand. Extracted evidence-drop-001.zip and read its EOCD record. The EOCD starts with PK\x05\x06. Search from the end, then read the 2-byte "total entries" field at offset +10:
i = b.rfind(b'PK\x05\x06')
total = struct.unpack_from('<H', b, i + 10)[0]

Result: 2. Submitted as d07-zip-001-zip-eocd-total-entries. CORRECT.

  1. First try at the timed modes. Added a zip_eocd solver to the one-answer driver run_mode.py. It returned no result: the Time Trial asked 11 different questions about 5 files, not one.
  2. Wrote run_meta.py, a composite driver. It does the whole loop for any mix of fields:
  3. Start the attempt (op=start for Single Solve, op=retry for the timed modes).
  4. Download the bundle.
  5. For each question, take the file name after -> in its artifact field (for example metadata-day-07-evidence.zip -> camera-001.jpg). Find it with find_file, which extracts with 7z x -y -pinfected and searches nested zips.
  6. Pick a handler from the answer ID. For example ...-md5 → hashlib.md5, ...-magic-prefix-hex-16 → fb[:16].hex(), ...sof-dimensions... → JPEG SOF parse, ...eocd-total-entries → the EOCD read above.
  7. Submit every answer in one JSON object.
  8. Time Trial. run_meta.py answered all 11. Examples from answers.json:

CORRECT.

  1. Mastery. IDs start with set1. or set2.. Each set has its own inner zip. The driver maps set N to the N-th inner zip, strips the prefix, computes the answer, and puts the prefix back. All 22 answered. CORRECT.

Results

ModeResultFlag
Single SolveCORRECTa402f1dbcfd5ccc361b3e2157b46d39f
Time TrialCORRECTcc3ed4df69afb1d06de32b2a56f9e589
MasteryCORRECTf0f2e213eb7669f064fe7fcf8ce5b1d9

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-07-seven-zip-no-relation time_trial /tmp/d07

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 parses the files. It never runs them.

Day 7: WebView Bridge

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: caesar.
{"schema":"huntress.mobile.puzzle.v1","day":7,"codec":"caesar","data":"KX]7BKPOK?>:CCP=;:@O","key":10}
  1. Decoded it. Shift every character back by key (10). For example K (75) becomes A (65).
import json
p = json.load(open('single-solve/huntress_puzzle.json'))
print(''.join(chr((ord(c) - p['key']) % 256) for c in p['data']))

Output: ANS-8AFEA54099F3106E.

  1. Submitted it under answer. The Game Master replied CORRECT.
  2. Taught the driver. Added the caesar codec to mobile_puzzle() in run_mode.py.
  3. Time Trial and Mastery: ran run_mode.py on both. Both came back CORRECT. The Time Trial answer was ANS-EF4F4D6A583828D4.

Results

ModeResultFlag
Single SolveCORRECT6640e170fc7ef9afdc8e733b3d022570
Time TrialCORRECT89e1a6e5b7a1eee5ffae6b49aae0a7f7
MasteryCORRECT71642323484b46ddfb868a5acd814c6f

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-07-webview-bridge single_solve mobile_puzzle /tmp/d07

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 7: Node by Node

Lane: Script analysis. Modes: Single Solve, Time Trial, Mastery. Result: all CORRECT.

The challenge

What we were given

escaped_octets|rolling_xor|ec
hex_array|single_byte_xor|3b
hex_buffer|reverse_bytes|
base64_chunks|reverse_bytes|

What was asked

How it was solved, start to finish

  1. Started the untimed Single Solve and downloaded the archive.
  2. Wrote a Node.js decoder (nodedec.py). It is the Bash decoder with extra material parsers:
  1. New role: persistence. node-schedule-descriptor.mjs decodes to build_schedule,register_descriptor. That is persistence_descriptor, mapped to T1053.003 (Scheduled Task/Job: Cron). Node's interpreter ID is T1059.007.
FileStepsRoleATT&CK
node-context.mjsdecode_configuration>return_configurationbenign_utilitynone
node-memory-stage.mjsacquire_remote>dispatch_memorystagerT1105
node-embedded-write.mjsdecode_embedded>write_filedropperT1140
node-remote-write.mjsacquire_remote>write_filedownloaderT1105
node-outbound-transfer.mjsread_file>transmit_remoteuploaderT1041
node-local-dispatch.mjslocate_local>dispatch_processlauncherT1059.007
node-schedule-descriptor.mjsbuild_schedule>register_descriptorpersistence_descriptorT1053.003
node-staged-chain.mjsprofile_host>acquire_remote>write_file>change_mode>dispatch_processstaged_chainT1059.007
  1. Advanced Bash. These configs start with v=1|feature=..., not v=1|steps=.... The old check rejected them, so all decoders were changed to accept any v=<n>|<key>= start. Decoded:
indirect-expansion.sh:  v=1|feature=indirect_expansion|primitive=parameter_indirection|campaign_id=BASHX-F434AEA9|stage_count=1|steps=recognize_syntax,reconstruct_intent
token-fragmentation.sh: v=1|feature=token_fragmentation|primitive=array_token_construction|campaign_id=BASHX-E4F52183|stage_count=1|steps=recognize_syntax,reconstruct_intent

Their role is the special value advanced_syntax, and ATT&CK is none.

  1. Two wiring fixes:

After that, all 469 answers were CORRECT. Real answers:

{"nodejs-persistence-role": "persistence_descriptor", "nodejs-persistence-attack": "T1053.003",
 "nodejs-persistence-adapter": "systemd_descriptor", "nodejs-persistence-schedule-path": "/etc/cron.d/node-f4b470",
 "bash-advanced-indirect-role": "advanced_syntax", "bash-advanced-indirect-feature": "indirect_expansion",
 "bash-advanced-indirect-primitive": "parameter_indirection"}
  1. Time Trial: five answers were missing at first, because the Node chain file did not decode in that variant. After that fix, token-fragmentation.sh failed on the same variant. The material parser was made more general, and the Time Trial passed.
  2. Mastery (938 questions, two sets):

Results

ModeResultFlag
Single SolveCORRECTd6506462aeb2a3e5c45b9f35274c81d1
Time TrialCORRECT6b39c0493fdaf4974978f1b7cb6654f3
MasteryCORRECT0a3cf17de369caad0674de448e827843

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

This rebuilds all 469 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-07-node-operation-graphs <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 7: Percent Chance

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. Standard percent-encoding (%XX hex pairs). URL-decode to get plaintext.
  2. Mastery blobs use multiple encodings from Days 1-7. 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