2026-10-02

Day 2: Mangled

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 the attempt (7b599670-77a3-4f4e-8c5f-a611ec6a8bb2) and downloaded the zip.
  2. Extracted it with 7z x -y -pinfected -oextracted evidence.zip, then hashed both files with sha256sum.
  3. C file (same steps as Day 1):
  1. C++ symbols: nm listed the mangled names. c++filt showed what they mean:
  1. Config (the new part): the C++ file has a section named .hcfg. It holds an HCFG record:
  2. Bytes 0–3 are HCFG. Byte 4 is the version. Byte 5 is the XOR key.
  3. Bytes 6–7 are the payload length and bytes 8–11 are the CRC32 (both little-endian). The payload starts at byte 12.
  4. XOR each payload byte with the key, check the CRC32, and parse the result as JSON.
i = data.find(b'HCFG')
key = data[i+5]; plen, crc = struct.unpack_from('<HI', data, i+6)
payload = bytes(b ^ key for b in data[i+12:i+12+plen])
assert zlib.crc32(payload) == crc
print(json.loads(payload))

Re-checked on the saved file with hcfg.py:

=== HCFG valid records in day02-cpp.elf ===
offset=0x2180 version=1 xor_key=0x31 plen=367 crc32=0x6149aa00
  JSON: {"campaign":"BR02-000","domain":"node-000.day02.example.invalid","ipv4":"198.51.100.40","url":"https://node-000.day02.example.invalid/api/BR02-000","mutex":"Global\\HuntressBR02_000", ...}
  1. Submitted the 17 answers in answers.json. Examples: "cpp_xor_key": "0x31", "cpp_config_crc32": "0x6149aa00", "vtable_symbol": "_ZTV15DiscoveryEngine". Result: CORRECT.
  2. Time Trial:
  1. Mastery:

Results

ModeResultFlag
Single SolveCORRECT95c8641ef1f5afd697437e2976468986
Time TrialCORRECT761b7c0feecc075175e39573ea0c9a1c
MasteryCORRECT (practice)c2520437aa1b82cde610d9fda7723627

Each mode folder has the zips, the extracted files, the answers, commands-output.md, and the raw Game Master responses. The Time Trial retries are saved as retry-2-* and retry-3-*. No screenshots were taken.

Note: single-solve/commands-output.md prints the zip hash with two characters missing. The correct value is the one above (it matches start-response.json and sha256sum).

Reproduce

cd single-solve
7z x -y -pinfected -oextracted evidence.zip
sha256sum extracted/*
readelf -p .huntress extracted/day01-c.elf
objdump -M intel -d --disassemble=recover_code extracted/day01-c.elf
nm extracted/day02-cpp.elf | grep -E 'score|vtable|typeinfo'
c++filt _ZNK15DiscoveryEngine5scoreEPKc _ZTV15DiscoveryEngine
python3 -I ~/.config/huntress/solvers/hcfg.py extracted/day02-cpp.elf

These commands only read the files. They never run them.

Day 2: Looks Can Be Deceiving

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. Started the attempt and noted the answer ID from the reply.
  2. Downloaded the zip and extracted its member. For Mastery, opened the outer bundle first, then each inner zip.
  3. Read the first 16 bytes of each assigned file and printed them as hex:
python3 -c 'from pathlib import Path; print(Path("single-solve/files/evidence-note.txt").read_bytes()[:16].hex())'
  1. Results per file:
FileFirst 16 bytes (hex)As text
evidence-note.txt48756e7472657373204d657461646174Huntress Metadat
roster.csv616e616c7973745f69642c636173655fanalyst_id,case_
evidence-note-copy.txt48756e7472657373204d657461646174Huntress Metadat
disguised-report.bin255044462d312e370a252048756e7472%PDF-1.7\n% Huntr
  1. Found the disguise. disguised-report.bin claims to be a .bin file, but it starts with %PDF-1.7. It is a PDF.
  2. Submitted one JSON object per mode. Mastery:
{
  "challenge": "metadata-forensics-day-02-looks-can-be-deceiving/mastery",
  "answers": {
    "set1.evidence-note-copy-magic-prefix-hex-16": "48756e7472657373204d657461646174",
    "set2.disguised-report-magic-prefix-hex-16": "255044462d312e370a252048756e7472"
  }
}
  1. The Game Master replied CORRECT each time and returned the flag.

Results

ModeResultFlag
Single SolveCORRECT3438d22184f1243a9c8fc30cdc9f54e9
Time TrialCORRECTce928a0b41a1376a68f70be80133f63b
MasteryCORRECTd6004ae265e59a49f8cf1efd57d4bc22

This folder keeps the zips and extracted files only. The Game Master JSON replies for Day 2 were not saved.

Reproduce

python3 -c 'from pathlib import Path; print(Path("time-trial/files/roster.csv").read_bytes()[:16].hex())'
python3 -c 'from pathlib import Path; print(Path("mastery/files/metadata-day-02-evidence-01.zip.contents/evidence-note-copy.txt").read_bytes()[:16].hex())'
python3 -c 'from pathlib import Path; print(Path("mastery/files/metadata-day-02-evidence-02.zip.contents/disguised-report.bin").read_bytes()[:16].hex())'

These only read bytes. run_meta.py later handles the same field type (-magic-prefix-hex-16 returns fb[:16].hex()).

Day 2: Deep Link Drift

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 attempt (Single Solve attempt ef3f32cd-7b0e-495d-859b-289cc82175d3) and downloaded the APK.
  2. Checked the hash with sha256sum. It matched the start response.
  3. Read the manifest with aapt dump xmltree. It shows an exported .ChallengeActivity with scheme huntress02, host deep-link-drift and path prefix /unlock.
  4. Read the puzzle asset:
unzip -p deep_link_drift.apk assets/huntress_puzzle.json
{"schema":"huntress.mobile.puzzle.v1","day":2,"codec":"reverse","data":"94AEE0A765B0097A-SNA"}
  1. Decoded it. New codec today: reverse. Reverse the string: 94AEE0A765B0097A-SNA → ANS-A7900B567A0EEA49.
  2. Submitted under answer. The Game Master replied CORRECT.
  3. Time Trial (attempt 0fd9e1f6-0216-45c2-b708-0a316040daf3): same steps. 44466DC53283AEC9-SNA → ANS-9CEA38235CD66444.
  4. Mastery (attempt 9fed887b-e073-45ef-8b9b-d48d2edfaadc): reversed the asset in each APK, then sent all three in one submit.
set1.answer  MOB-02-285188CF6B  data 28E64C9FF60E34F9-SNA  answer ANS-9F43E06FF9C46E82
set2.answer  MOB-02-5144692789  data 519F497B87D0CC07-SNA  answer ANS-70CC0D78B794F915
set3.answer  MOB-02-47421FF0E6  data 4E80D7F727DE7C25-SNA  answer ANS-52C7ED727F7D08E4

Results

ModeResultFlag
Single SolveCORRECT7d214fa8d5d1785a754c73374679bccb
Time TrialCORRECTb4e4e338ff1748f180d36857d2550db6
MasteryCORRECT64d3d8f9f9e8494dbacaeb4203c7f08a

Each mode folder has the APK(s), answers.json, start-response.json, submit-response.json, final-status-response.json and a commands-output.md. No screenshots were taken.

Reproduce

Offline, from the saved APK:

unzip -p single-solve/deep_link_drift.apk assets/huntress_puzzle.json
python3 -I -c 'print("94AEE0A765B0097A-SNA"[::-1])'

A fresh run with the later lane driver (it handles the reverse codec):

python3 -I ~/.config/huntress/solvers/run_mode.py mobile-android-day-02-deep-link-drift single_solve mobile_puzzle /tmp/d02

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 2: Host With the Most

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

The challenge

What we were given

FileRole it plays
host-context.jsbenign
memory-stage.jsstager
embedded-write.jsdropper
remote-write.jsdownloader
local-dispatch.jslauncher
outbound-transfer.jsuploader
impact-plan.jsimpact
staged-handoff.jschain
relay-handoff.jsrelay

What was asked

How it was solved, start to finish

  1. Started the untimed attempt dd3825ea-49e3-4c47-a202-60d367f89ada at 2026-10-02T16:46:32Z.
  2. Downloaded and extracted evidence.zip with 7z. The extracted files are saved in single-solve/.
  3. PowerShell: decoded the Base64 JSON descriptor in each .ps1 file, the same way as Day 1.
  4. JScript: decoded each config statically, then read three things from it:

The scripts were never run. The decoded graphs and the saved answers (re-checked offline with tools/jsdec_py_emu.py):

FileDecoded stepsAdapterRoleATT&CK
host-context.jsdecode_configuration>return_configurationScripting.Dictionarybenign_utilitynone
memory-stage.jsacquire_remote>dispatch_memoryMSXML2.XMLHTTP.6.0stagerT1105
embedded-write.jsdecode_embedded>write_fileADODB.StreamdropperT1140
remote-write.jsacquire_remote>write_fileMSXML2.XMLHTTP.6.0downloaderT1105
local-dispatch.jslocate_local>dispatch_processregsvr32.exelauncherT1059.007
outbound-transfer.jslocate_local>prepare_transfer>upload_remoteCertReq.exeuploaderT1041
impact-plan.jsenumerate_targets>transform_content>write_recovery_noteADODB.StreamimpactT1486
staged-handoff.jsacquire_remote>write_file>dispatch_process>handoff_scriptMicrosoft.XMLHTTPstaged_chainT1059.007
relay-handoff.jssame as aboveWinHttp.WinHttpRequest.5.1staged_chainT1059.007
  1. Handoffs ("which script hands off to which"): the chain and relay files name their next stage. staged-handoff.js hands off to resource-sample.ps1 (another language). relay-handoff.js hands off to local-dispatch.js (same language).
  2. Syntax questions: read straight from the source text. Examples: function inspect_x(...) is a declaration, and var inspect_x = function(...) is an anonymous expression. A .call( or .apply( on the descriptor-recovery call sets the invocation style.
  3. Answers. A few real ones from single-solve/answers.json:
{"jscript-stager-role": "stager", "jscript-stager-attack": "T1105",
 "jscript-stager-adapter": "MSXML2.XMLHTTP.6.0", "jscript-stager-campaign": "campaign-a3a04f5ced",
 "jscript-stager-url": "https://a3a04f5ced.example.invalid/36925272.dat",
 "jscript-stager-function-style": "anonymous_expression", "jscript-stager-invocation-style": "apply",
 "jscript-stager-property-style": "dot",
 "jscript-chain-next-stage": "resource-sample.ps1", "jscript-relay-next-stage": "local-dispatch.js"}
  1. Submitted all 87 answers under their exact IDs. The Game Master replied CORRECT.
  2. Time Trial: attempt c38b2d1e-db06-44d6-ad00-ff6126e377b5. The deadline was 5 seconds after the start (2026-10-02T17:05:59.336Z). New evidence.zip, SHA-256 9bb6e0a84469b3f4695cc3acf6f99dccfb8e3f4a6fa650357a1d6871592b3423. Same steps. The client measured 1.48 seconds from retry to submit.
  3. Mastery: attempt d930eed5-fdbd-46ec-b996-945353925bb0, 174 questions in two sets. The deadline was 6 seconds after the start (2026-10-02T17:11:10.515Z). Two archives:

Both sets were decoded and submitted together. The client measured 1.84 seconds.

Results

ModeResultFlag
Single SolveCORRECT3b388ccd7af0941e48b66023d9721370
Time TrialCORRECTf02d8773484e5485c18a507164564777
MasteryCORRECT4a858c1eee015ee32e66489eda62cef8

Saved responses:

Each mode also keeps its archives and extracted files. No screenshots were taken.

Reproduce

Offline, from the repo root, using the saved Single Solve archive:

mkdir -p /tmp/d02/ex
7z x -pinfected -o/tmp/d02/ex repos/day-02-script-analysis-host-with-the-most/single-solve/evidence.zip
python3 -I tools/solve_expansion.py /tmp/d02/ex \
  repos/day-02-script-analysis-host-with-the-most/single-solve/start-response.json /tmp/d02/answers.json

This rebuilds all 87 saved answers (re-checked on 2026-11-01). It reads the scripts as text only. In the tools/ copy, JScript is decoded by jsdec_py_emu.py (pure Python).

Day 2 — Half a Turn (ROT13)

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

> Thirteen steps forward. Funny how that works out.

What we were given

A text blob to decode. Each mode provides one or more blobs.

How it was solved

The title "Half a Turn" and the hint "thirteen steps" point to ROT13 — rotating each letter 13 positions in the alphabet (half of 26).

  1. Downloaded blob.txt from the Game Master.
  2. Applied ROT13 decoding to the entire file contents.
  3. The decoded text ends with a slug in the format word-word-word-NN.
  4. Submitted the slug as the answer.

For mastery, 8 blobs were provided in a zip file. Each was independently ROT13-decoded and its slug submitted.

Automated with warmup_decode.py — a general-purpose decoder that handles ROT13, hex, base64, and 25+ other encoding types across the warmup lane.

Results

ModeResultFlag
Single SolveCORRECTaee569db2b23f0dfcffd232b700eac37
Time TrialCORRECT7f00336a7a5cd16995653ba5544878fe
Mastery (8 blobs)CORRECT4a88ed9065ca958928bfb5612f591dfd