2026-10-11

Day 11: D-Day

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. Started an attempt with the Game Master (op=start). It returned the prompt and all 110 questions as JSON.
  2. Downloaded the artifact (op=artifact) and extracted it with 7z.
  3. Answered the routine questions with the binary solver built up over Days 1–10 (solve_tm.py):
  1. Solved the new d11 part. The question spelled out the record layout, so it could be followed step by step:
  2. Search the d11 file for long Base64 strings (100 or more characters).
  3. Decode each one. One decodes to bytes that start with HCFG.
  4. Read the record header: version (1 byte), XOR key (1 byte), payload length (2 bytes), CRC32 (4 bytes). The payload follows.
  5. XOR the payload with the key, check the CRC32, and parse the result as JSON.
for m in re.finditer(rb'[A-Za-z0-9+/]{100,}={0,2}', data):
    dec = base64.b64decode(m.group(0))
    if dec[:4] != b'HCFG': continue
    key = dec[5]; plen, crc = struct.unpack_from('<HI', dec, 6)
    payload = bytes(b ^ key for b in dec[12:12+plen])
    assert zlib.crc32(payload) == crc
    print(m.start(), json.loads(payload))

Output: the Base64 string starts at offset 368272, the XOR key is 0x71, and the CRC32 is 0x03663005. The decoded config:

{"campaign": "BR11-000", "domain": "node-000.day11.example.invalid",
 "ipv4": "198.51.100.220", "url": "https://node-000.day11.example.invalid/api/BR11-000",
 "mutex": "Global\\HuntressBR11_000", "service": "HuntressLab-Day11-000", "host_model": "workstation"}

The config answers were these fields, plus the CRC32 and the offset.

  1. Submitted all 110 answers as one JSON object. The Game Master replied CORRECT and returned the flag.
  2. Time Trial and Mastery: these use the same steps on freshly generated samples, under a timer. The driver run_tm.py does start → download → solve → submit in one go.

Results

ModeResultFlag
Single SolveCORRECT6f8200a3c64a9105417bb8ae0ede01e1
Time TrialCORRECT0505ed29e6337f05a4ba90a746dbda8d
MasteryCORRECTe809e64c678a068057b3c0e7d2d91c16

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

Reproduce

python3 -I ~/.config/huntress/solvers/run_tm.py binary-reverse-engineering-day-11-d-collection-planner single_solve /tmp/d11

This needs a Game Master token in ~/.config/huntress/gm-token. It only parses the samples and never runs them.

Day 11: What's My Name Again?

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: version resource strings are stored as UTF-16LE. The key name OriginalFilename is followed by NUL padding and then the value.

  1. Added a UTF-16 version-string reader to run_meta.py:
def version_string(fb, field):              # field = 'OriginalFilename'
    key = field.encode('utf-16le')
    i = fb.find(key)
    if i < 0: return None
    j = i + len(key)
    while j + 1 < len(fb) and fb[j:j+2] == b'\x00\x00': j += 2   # skip NUL + padding
    out = bytearray()
    while j + 1 < len(fb):
        ch = fb[j:j+2]
        if ch == b'\x00\x00': break
        out += ch; j += 2
    return out.decode('utf-16le', 'replace') or None

The handler picks the field from the answer ID: ...-version-original-filename → OriginalFilename. The same table also maps company-name, product-name, file-version, product-version, internal-name and file-description.

  1. Single Solve. telemetry-agent-001.exe → pe-base-386.exe. CORRECT.
  2. Time Trial. telemetry-agent-002.exe → pe-base-amd64.exe. CORRECT.
  3. Mastery. telemetry-agent-003.exe → pe-base-arm64.exe, telemetry-agent-004.exe → pe-base-386.exe. CORRECT.

So the random file names hide builds whose own resources say pe-base-386.exe, pe-base-amd64.exe and pe-base-arm64.exe.

Results

ModeResultFlag
Single SolveCORRECTfd93317313ad8ac8165614af09fd059c
Time TrialCORRECT1e48bc2d930807b22e9c3a46546ff9f9
MasteryCORRECTdfdbd47b28834174d2073c7e9986e4fd

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/run_meta.py metadata-forensics-day-11-whats-my-name-again single_solve /tmp/d11

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 searches the .exe bytes. It never runs them.

Day 11: Local Secrets

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 with key 81 (Day 4 used xor with key 29).
{"schema":"huntress.mobile.puzzle.v1","day":11,"codec":"xor","data":"EB8CfGkXY2NkZmVmYBUXZWkVYGU=","key":81}
  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-8F2257471DF48D14.

  1. Ran the lane driver for all three modes. A helper agent ran it once per mode:
python3 -I ~/.config/huntress/solvers/run_mode.py mobile-android-day-11-local-secrets <mode> mobile_puzzle <workdir>

The driver downloads each APK, reads its puzzle, decodes it by its codec, and submits all answers at once.

  1. Results: Single Solve (ANS-8F2257471DF48D14), Time Trial (ANS-57678213871E17EC) and all three Mastery answers came back CORRECT.

Results

ModeResultFlag
Single SolveCORRECT47d93eb4877742ff8631ac176deea554
Time TrialCORRECT744b8f9456b9c93300f5f6cf70b6482d
MasteryCORRECT5a02d337ee2a83fa7754c5f17065d066

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-11-local-secrets single_solve mobile_puzzle /tmp/d11

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 11: By Any Other Name

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 TypeScript files carry the usual marker. The only new work that day was in the metadata lane.
  1. Submitted. The Single Solve was CORRECT (811/811).
  1. Real answers from single-solve/answers.json:
{
 "polyglot-typescript-staged-chain-role": "staged_chain",
 "polyglot-typescript-staged-chain-attack": "T1059",
 "polyglot-typescript-staged-chain-adapter": "operation_graph",
 "polyglot-typescript-staged-chain-campaign": "TYPESCRIPT-aa5043eb",
 "polyglot-typescript-staged-chain-url": "https://typescript-aa5043eb9b.example.invalid/stage",
 "polyglot-typescript-staged-chain-stage-count": "3",
 "polyglot-typescript-staged-chain-steps": "decode_embedded>write_file>dispatch_process",
 "polyglot-typescript-staged-chain-host-profile": "standalone"
}
  1. Time Trial and Mastery used the same solver on fresh variants.

Results

ModeResultFlag
Single SolveCORRECT167c4e9dc20bc56b6f7a7bff930a50a2
Time TrialCORRECT796d90e7836b88013cdae94225ae6243
MasteryCORRECT2a963cf2f2851f2b9530d1a94eed0b06

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

This rebuilds all 811 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 11: Safe Travels

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. URL-safe base64 variant (- and _ instead of + and /). Standard base64url decode.
  2. Mastery blobs use multiple encodings from Days 1-11. 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