2026-10-18

Day 18: Flow State

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. Made the downloads robust (the fix for this day). With ~33 MB bundles, a download could arrive cut short. run_tm.py now:
  1. d01–d17 were answered as on Day 17.
  2. d18 config: a literal record, found by the normal scan. Re-checked on the copy from the Day 19 bundle with hcfg.py:
=== HCFG valid records in d18--variant-000.elf ===
offset=0x2140 version=1 xor_key=0x31 plen=367 crc32=0xd55cf099
  JSON: {"campaign":"BR18-000","domain":"node-000.day18.example.invalid","ipv4":"198.51.100.90","url":"https://node-000.day18.example.invalid/api/BR18-000","mutex":"Global\\HuntressBR18_000", ...}

0x2140 is 8512. Answers: format elf, XOR key 0x31, version 1, hcfg_offset 8512, campaign BR18-000.

  1. Submitted all 216 answers (answers.json). Result: CORRECT.
  2. Time Trial: a fresh variant, same steps. Result: CORRECT.
  3. Mastery: four deliveries (864 answers), same steps. Result: CORRECT.

Results

ModeResultFlag
Single SolveCORRECTbae5ac55252bd7a7c3605dc49d07453a
Time TrialCORRECT3d99da461084ca1878d7d089dc31bbec
MasteryCORRECT082390eb12c9ca5eb65914306f4e7855

Each mode folder has the raw start-response.json, answers.json, submit-response.json and final-status-response.json. The evidence zips were not saved for this day.

Reproduce

The Day 18 bundle was not saved, so a full offline re-run is not possible. The d18 config can be checked from the Day 19 bundle (from this folder):

mkdir -p /tmp/d18 && 7z x -y -pinfected -o/tmp/d18 ../day-19-binary-jack-in-the-box/single-solve/evidence.zip 'd18--*'
sha256sum /tmp/d18/d18--variant-000.elf   # 00882cd9…, same as d18_artifact_sha256_1
python3 -I ~/.config/huntress/solvers/hcfg.py /tmp/d18/d18--variant-000.elf

Live driver:

python3 -I ~/.config/huntress/solvers/run_tm.py binary-reverse-engineering-day-18-control-flow-reconstruction single_solve /tmp/d18

This needs a Game Master token in ~/.config/huntress/gm-token. Both only parse the files and never run them.

Day 18: Frame of Reference

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: take the width and height of the first video stream from the container, using ffprobe.

  1. Added a second ffprobe handler to run_meta.py. It asks for stream v:0 and prints width and height joined by x:
r = subprocess.run(['ffprobe', '-v', 'quiet', '-select_streams', 'v:0',
                    '-show_entries', 'stream=width,height', '-of', 'csv=p=0:s=x', tf.name],
                   capture_output=True, text=True, timeout=30)
return r.stdout.strip() or None
  1. Single Solve. video-001.mp4 → 320x180. CORRECT.
  2. Time Trial and Mastery. Helper agents ran run_meta.py. It answered all 23 and all 115. The video size was 320x180 in every set. Example synthesis answer (Time Trial): ["video-001.mp4","evidence-note.txt","installer-001.msi","panel-001.png"]. Both CORRECT.

Results

ModeResultFlag
Single SolveCORRECT3364ee636ea58aaeb4893495266645fd
Time TrialCORRECT757f8651706f9fb064d8fba77c6b5b47
MasteryCORRECT68d2e2aa477fd2a6bf55cfa4c26abc3f

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

ffprobe -v quiet -select_streams v:0 -show_entries stream=width,height -of csv=p=0:s=x video-001.mp4
python3 -I ~/.config/huntress/solvers/run_meta.py metadata-forensics-day-18-frame-of-reference single_solve /tmp/d18

The second line 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. ffprobe only reads the container headers.

Day 18: Encrypted Strings

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 xor, this time with key 20.
{"schema":"huntress.mobile.puzzle.v1","day":18,"codec":"xor","data":"VVpHOSZVJyAjIldRJSwjIyJXJ1c=","key":20}
  1. Decoded it: Base64-decode data, then XOR every byte with key.
import json, base64
p = json.load(open('single-solve/huntress_puzzle.json'))
print(bytes(b ^ p['key'] for b in base64.b64decode(p['data'])).decode())

Output: ANS-2A3476CE18776C3C.

  1. Ran the lane driver for all three modes. It already handled xor:
python3 -I ~/.config/huntress/solvers/run_mode.py mobile-android-day-18-encrypted-strings <mode> mobile_puzzle <workdir>
  1. Results: Single Solve (ANS-2A3476CE18776C3C), Time Trial (ANS-8889E945197A9A9E) and all five Mastery answers came back CORRECT.

Results

ModeResultFlag
Single SolveCORRECT9d051ec3a0a1eff6f74952577dd6e766
Time TrialCORRECTdd78bef57e1bdc88d0433034788fa60b
MasteryCORRECTf2902f8beb9dd5774c335d23b666c86c

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-18-encrypted-strings single_solve mobile_puzzle /tmp/d18

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 18: Orphan Process

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. The Single Solve crashed. Some host and polyglot files had no HUNTRESS_ANALYSIS_V1:<ENC>- marker. Instead they had a HUNTRESS_ANALYSIS_V1:SPLIT comment and an array of string chunks. Real lines from polyglot-google_apps_script-downloader.gs:
const HUNTRESS_ANALYSIS_V1_SPLIT_22eaee83 = [
    "FRAG-763d337c6c616e6775616765.3d676f6f676c655f61707073.5f7363726",
    "970747c726f6c65.3d646f776e6c6f616465727c.766572646963743d7375737",
    ...
  1. Fixed hostpgdec.py. Join the chunks in order. The result is the normal <ENC>-<data> payload (here FRAG-...), which then decodes as before:
am = re.search(r'HUNTRESS_ANALYSIS_V1_SPLIT_\w+\s*=\s*\[(.*?)\]', text, re.S)
joined = ''.join(re.findall(r'"([^"]*)"', am.group(1)))   # "FRAG-763d337c..."
enc, data = re.match(r'([A-Z0-9]+)-(.+)$', joined, re.S).groups()

Decoded, the Google Docs host gives:

v=3|language=google_apps_script|role=staged_chain|verdict=suspicious|attack=T1059|adapter=operation_graph|host_profile=google_docs_sidebar|obfuscation_profile=fragmented_hex|stage_profile=cross_language_handoff|next_language=jscript|stage_count=3|steps=profile_host,decode_configuration,dispatch_language|...
  1. Submitted. The Single Solve was CORRECT.
  1. The timed modes first got HTTP 409. Many lanes were running at once and an attempt was still active. A re-run went through.
  1. Real answers from single-solve/answers.json:
{
 "host-google-docs-sidebar-google-apps-script-role": "staged_chain",
 "host-google-docs-sidebar-google-apps-script-attack": "T1059",
 "host-google-docs-sidebar-google-apps-script-adapter": "operation_graph",
 "host-google-docs-sidebar-google-apps-script-campaign": "GOOGLE_APPS_SCRIPT-29193ae3",
 "host-google-docs-sidebar-google-apps-script-url": "https://google_apps_script-29193ae3e0.example.invalid/stage",
 "host-google-docs-sidebar-google-apps-script-stage-count": "3",
 "host-google-docs-sidebar-google-apps-script-steps": "profile_host>decode_configuration>dispatch_language",
 "host-google-docs-sidebar-google-apps-script-host-profile": "google_docs_sidebar"
}
  1. Time Trial and Mastery used the same solver on fresh variants.

Results

ModeResultFlag
Single SolveCORRECT5aecf682b19d394d0160295a0886e3d8
Time TrialCORRECT6212f301fb57dfde703bea47d3e8adc5
MasteryCORRECT050a663b95a0252f722562745b602520

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

This rebuilds all 1,194 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 18: Off the Rails

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. Characters are interleaved across 2 rails. First half of the string is the top rail (even positions), second half is the bottom rail (odd positions). Re-interleave to decode.
  2. Mastery blobs use multiple encodings from Days 1-18. 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