2026-10-14

Day 14: Selective Memory

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–d13 were answered as on Day 13.
  3. d14 config: the question said to scan for a literal HCFG and accept the first valid record. Here it sits in its own .hcfg section. Re-checked on the saved sample:
HCFG offset=4000 version=1 xor_key=0xa1 len=367 crc32=0x79f491da
section of match: .hcfg
JSON: {"campaign":"BR14-000","domain":"node-000.day14.example.invalid","ipv4":"198.51.100.20","url":"https://node-000.day14.example.invalid/api/BR14-000","mutex":"Global\\HuntressBR14_000", ...}
  1. d14 section check: the Day 10 has_hcfg_section code reads the section names, so the answer was true.
  2. Answers for d14: format elf, architecture x86-64, has_hcfg_section true, CRC32 0x79f491da, campaign BR14-000.
  3. Submitted all 140 answers (answers.json). Result: CORRECT.
  4. Time Trial: a fresh variant, same steps. Result: CORRECT.
  5. Mastery: five deliveries (700 answers), same steps. Result: CORRECT.

Results

ModeResultFlag
Single SolveCORRECTa1895cef4c7b9ba5d7eced20feb8432f
Time TrialCORRECTee069c5160da6212762b442acdbf6c7d
MasteryCORRECT14978c42a0caa6dbb550f8b8993d5269

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

Checked on 2026-11-01: this gives the same 140 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-14-objective-c-persistence-descriptor single_solve /tmp/d14

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

Day 14: The Shortcut Home

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: a .lnk file stores its target in the LinkInfo block as a local base path. Read it from the bytes.

  1. Wrote a small LNK parser, lnk_target.py:
  2. Check the header: the file starts with 4C 00 00 00.
  3. Read the LinkFlags at 0x14.
  4. If the flag HasLinkTargetIDList (0x1) is set, skip the ID list (2-byte size + data) that starts at 0x4C.
  5. If HasLinkInfo (0x2) is set, read the LinkInfo block. When its VolumeIDAndLocalBasePath flag is set, read the LocalBasePath string at the stored offset.
  6. Add the CommonPathSuffix string. If the LinkInfo header is 0x24 bytes or more, prefer the Unicode base path.
flags = struct.unpack_from('<I', b, 0x14)[0]
pos = 0x4c
if flags & 0x1: pos += 2 + struct.unpack_from('<H', b, pos)[0]   # skip IDList
if flags & 0x2:
    li = pos
    lbp_off = struct.unpack_from('<I', b, li + 0x10)[0]           # LocalBasePath
    cps_off = struct.unpack_from('<I', b, li + 0x18)[0]           # CommonPathSuffix
  1. Tested it on the Single Solve file. shortcut-001.lnk → C:\Windows\System32\cmd.exe. CORRECT.
  2. Wired it into run_meta.py. Answer IDs with lnk-target call target_path(). All other fields used the existing handlers.
  3. Time Trial and Mastery. run_meta.py answered all 19 and all 95. The LNK target was C:\Windows\System32\cmd.exe in every set. Example synthesis answers: Time Trial ["document-001.pdf","shortcut-001.lnk","evidence-note.txt"], mastery set 1 ["shortcut-001.lnk","evidence-note.txt","document-001.pdf"]. Both CORRECT.

Results

ModeResultFlag
Single SolveCORRECTdd433920a61ec2c8b76ce90c1a09744e
Time TrialCORRECT4766855aec3314855c0a2174a2a3591e
MasteryCORRECTd1567c6181898e2102a2822f6c9a7718

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/lnk_target.py shortcut-001.lnk
python3 -I ~/.config/huntress/solvers/run_meta.py metadata-forensics-day-14-shortcut-home single_solve /tmp/d14

The first line only needs the extracted .lnk. 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 opens the shortcut in Windows.

Day 14: Predictable Crypto

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 caesar with key 9 (Day 7 used key 10).
{"schema":"huntress.mobile.puzzle.v1","day":14,"codec":"caesar","data":"JW\\6L><BL=A;OL>NN:=?","key":9}
  1. Decoded it. Shift every character back by key. For example J (74) 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-C539C482FC5EE146.

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

Single Solve and Time Trial came back CORRECT.

  1. Fixed a Mastery crash. Mastery crashed inside the Base64 step. Some sets carried Base64 that was not clean (padding and other malformed input). The Base64 decode in mobile_puzzle() was hardened, then Mastery was run again. The hardened lines in run_mode.py:
dd=''.join(pj['data'].split()).replace('-','+').replace('_','/')  # strip ws, url-safe
if len(dd)%4==1: dd=dd[:-1]                                       # drop stray trailing char
raw=base64.b64decode(dd + '='*(-len(dd)%4), validate=False)

It strips whitespace, accepts URL-safe characters, drops a stray last character, and adds missing = padding.

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

Results

ModeResultFlag
Single SolveCORRECT3adc5ad417817e22db9226cdf0f10cbd
Time TrialCORRECT5dc49487045a8e3ec3a1b9ff0d2268af
MasteryCORRECT227c27f165ce1fba33b1cfb409a92b09

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-14-predictable-crypto single_solve mobile_puzzle /tmp/d14

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 14: Trust the 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. No new code was needed. The MSBuild .proj files carry the usual marker.
  1. Ran run_expansion.py for all three modes. All three came back CORRECT.
  1. Real answers from single-solve/answers.json:
{
 "polyglot-msbuild_xml-staged-chain-role": "staged_chain",
 "polyglot-msbuild_xml-staged-chain-attack": "T1059",
 "polyglot-msbuild_xml-staged-chain-adapter": "operation_graph",
 "polyglot-msbuild_xml-staged-chain-campaign": "MSBUILD_XML-984e0b62",
 "polyglot-msbuild_xml-staged-chain-url": "https://msbuild_xml-984e0b6296.example.invalid/stage",
 "polyglot-msbuild_xml-staged-chain-stage-count": "2",
 "polyglot-msbuild_xml-staged-chain-steps": "acquire_remote>dispatch_process",
 "polyglot-msbuild_xml-staged-chain-host-profile": "standalone"
}
  1. Time Trial and Mastery used the same solver on fresh variants.

Results

ModeResultFlag
Single SolveCORRECTd00c06c24a63ee4f1dafcdabbcc583e2
Time TrialCORRECT44e6cc3d28acf695d5af568bb6bc2929
MasteryCORRECT4cca9097328a024d16ef5ddd690904f9

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/d14/ex
7z x -pinfected -o/tmp/d14/ex evidence.zip
python3 -I tools/solve_expansion.py /tmp/d14/ex start-response.json /tmp/d14/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 14 — Seven Steps (Caesar Cipher Variant)

Lane: Warmups · Challenge ID: warmups-day-14

> Caesar took a week off.

What we were given

A text blob encoded with a shifted cipher. Each blob uses a different Caesar shift value.

How it was solved

"Caesar took a week off" — a week is 7 days, so this is a Caesar cipher with shift 7 (ROT7 instead of the usual ROT13).

  1. Downloaded the blob from the Game Master.
  2. The blob contains fragments that are additionally transformed with per-fragment ciphers (reverse, atbash, or further Caesar shifts).
  3. Auto-detected the shift value by trying all 26 rotations and scoring against English letter frequency / known slug vocabulary.
  4. Decoded each fragment, reassembled the plaintext, and extracted the answer slug.

For mastery, multiple blobs were decoded independently. Slug words were disambiguated against the observed CTF vocabulary when the shift produced near-matches.

Automated with warmup_decode.py.

Results

ModeResultFlag
Single SolveCORRECT13d100f8ceb18f836e51952aec06edee
Time TrialCORRECT7b42fabbb3290101ebc3061c34182ad4
MasteryCORRECTf43bb754e48931c07dfcb4dcfea61fa6