2026-10-13
Day 13: Crystal Clear
Lane: Binary reverse engineering. Modes: Single Solve, Time Trial, Mastery. Result: all CORRECT.
The challenge
- ID:
binary-reverse-engineering-day-13-crystal-dns-configuration - Prompt: "Crystal compiles to native code with a distinctive shine. Fingerprint the runtime, then follow the DNS labels — this one has somewhere it wants to resolve."
What we were given
- One
evidence.zip(32,241,637 bytes, SHA-2561aea8fe529bf0f679d23936a1dfcb2b97826b240bca464279eb7de9d0efa2902). AES encrypted, passwordinfected. - The earlier files again:
d01tod12. - New today:
d13--variant-000.elf(749,208 bytes), a 64-bit Linux program written in Crystal.
What was asked
- 130 questions in Single Solve and Time Trial. Mastery had five deliveries, so 650.
- Question types:
- Hashes: SHA-256 of each member.
- d01 to d12: the same questions as Day 12.
- d13 (new): machine, architecture, format (lowercase token), the config fields, the CRC32, and
hcfg_offset.
How it was solved, start to finish
- Ran the driver
run_tm.py: start the attempt, download the zip, runsolve_tm.py, submit. - d01–d12 were answered as on Day 12.
- d13 config: this one is Base64 again (like Day 8 and Day 9). The question said to Base64-decode every run of 100+ Base64 characters and accept the first that decodes to a CRC32-valid
HCFGrecord.
- The saved Crystal sample has no plain
HCFGat all. The record exists only as Base64. - The offset to report is where the Base64 string starts.
Re-checked on the saved sample:
[base64 run at file offset 560188, run length 508]
HCFG version=1 xor_key=0x91 len=368 crc32=0xa69b7e61
section of match: .rodata
JSON: {"campaign":"BR13-000","domain":"node-000.day13.example.invalid","ipv4":"198.51.100.240","url":"https://node-000.day13.example.invalid/api/BR13-000","mutex":"Global\\HuntressBR13_000", ...}
Answers: format elf, d13_analysis_hcfg_offset = 560188, CRC32 0xa69b7e61, campaign BR13-000.
- Same code paths as before: the Base64 scan (Days 8–9) and the lowercase format token (Day 12) handle this specimen.
- Submitted all 130 answers (
answers.json). Result:CORRECT. - Time Trial: a fresh variant, same steps. Result:
CORRECT. - Mastery: five deliveries (650 answers), same steps. Result:
CORRECT.
Results
| Mode | Result | Flag |
|---|---|---|
| Single Solve | CORRECT | e90a1d71b26f714fa22ca48d25ffdd81 |
| Time Trial | CORRECT | 19105c22b99fe95b146ac24b65fcbc79 |
| Mastery | CORRECT | be2d0e037e64dec9a723f2bcc8a30745 |
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/d13/deliveries && cp single-solve/evidence.zip /tmp/d13/deliveries/delivery-1.zip
python3 -I ~/.config/huntress/solvers/solve_tm.py single-solve/start-response.json /tmp/d13/deliveries /tmp/d13/answers.json
Checked on 2026-11-01: this gives the same 130 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-13-crystal-dns-configuration single_solve /tmp/d13
This needs a Game Master token in ~/.config/huntress/gm-token.
Day 13: Product Placement
Lane: Metadata forensics. Modes: Single Solve, Time Trial, Mastery. Result: all CORRECT.
The challenge
- ID:
metadata-forensics-day-13-product-placement - Prompt: "Installers were copied, renamed, and repackaged. Recover stable product identities, distinguish revisions from different products, and find the collision."
What we were given
- Single Solve:
(evidence.zipmetadata-day-13-evidence.zip, 3,339 bytes, SHA-2566e401e69ecf6c3d048c285a950a3cc10611da4a070b7e10d2d69aa5b26bac954) withinstaller-001.msi. - Time Trial:
evidence.zip(604,379 bytes, SHA-2568113168f492b5d90076d6c1ed896967a7f938d8880be4f0b060731e291631748). It holds one file of each type so far: evidence notes,roster.csv,camera-001.jpg,panel-001.png,document-001.pdf,evidence-drop-001.zip,telemetry-agent-001.exe,managed-001.dllandinstaller-001.msi. - Mastery:
metadata-forensics-day-13-product-placement-mastery.zip(3,022,449 bytes, SHA-25623f6f47cba3d1ed08f47215d61d56a58e0f76afada29a93ffaeaa41f90b64fe2). Five inner zips,evidence-01.ziptoevidence-05.zip, one per set. - New today: Windows Installer (
.msi) files.
What was asked
- Single Solve: 1 question:
msi.product_code_guidforinstaller-001.msi. - Time Trial: 18 questions. Mastery: 90 (5 sets × 18).
- Question types:
- File identity: filename, size, MD5, SHA-1, SHA-256, first 16 bytes, UTF-8 BOM.
- Headers: JPEG SOF, PNG IHDR, PDF version, ZIP EOCD entries, ZIP member names.
- Windows/.NET: PE machine, PE entry point, PE
OriginalFilename, .NET MVID. - New: MSI
ProductCode. - New: a "synthesis" question, for example: "Compute the full-file SHA-256 digest of each named file, then submit a compact JSON array of their filenames in ascending digest order. Files: [\"evidence-note.txt\",\"panel-001.png\",\"installer-001.msi\"]".
How it was solved, start to finish
- Wrote an MSI reader,
msi_product.py(no third-party libraries). An MSI file is an OLE2 compound file with database tables inside: - Parse the OLE2 header: sector size, FAT, DIFAT, mini-FAT and the directory.
- Decode the stream names. MSI packs table names into special Unicode ranges (
0x3800–0x4840). - Read
_StringPooland_StringDatato build the string table. - Read the
Propertytable. It has 2 columns stored column by column, and each cell is a string index (2 bytes, or 3 for very large pools). - Return the value in the row whose key is
ProductCode. - Single Solve.
installer-001.msi→{DD1A80D5-0250-4F4D-B289-13096D633C61}. This is the native form: braces and capitals.CORRECT. Then the reader was added torun_meta.py(product-code→product_property(fb, 'ProductCode')). - Time Trial, first run. It had the new synthesis question, which the driver did not know yet. Mastery also hit an HTTP 409 because other agents were using the Game Master at the same time.
- Added the synthesis handler. It reads the file list from the question text, hashes each file and sorts by digest:
q = QTEXT.get(aid, '') # question text by answer ID
files = json.loads('[' + re.search(r'\[([^\]]*)\]', q).group(1) + ']')
pairs = sorted((hashlib.sha256(find_file(bundle, n)).hexdigest(), n) for n in files)
return json.dumps([n for _, n in pairs], separators=(',', ':'))
The driver also had to fill QTEXT from the start reply, so the handler can see the question text.
- Re-ran the Time Trial and Mastery. Examples:
- Time Trial synthesis:
["evidence-note.txt","panel-001.png","installer-001.msi"]. - Mastery set 2 synthesis:
["panel-001.png","installer-001.msi","evidence-note.txt"]. ProductCodewas{DD1A80D5-0250-4F4D-B289-13096D633C61}in every set.
Both CORRECT.
Results
| Mode | Result | Flag |
|---|---|---|
| Single Solve | CORRECT | 08f8cae6e366a7ce09136c4c624594d5 |
| Time Trial | CORRECT | c63c8204795f6b769fd65ae5a3ed4764 |
| Mastery | CORRECT | 26d7b8df8df6c48e76403ddc961691cf |
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/msi_product.py installer-001.msi ProductCode
python3 -I ~/.config/huntress/solvers/run_meta.py metadata-forensics-day-13-product-placement single_solve /tmp/d13
The first line only needs the extracted .msi. 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 installs or runs the MSI.
Day 13: Keystore Misuse
Lane: Mobile (Android). Modes: Single Solve, Time Trial, Mastery. Result: all CORRECT.
The challenge
- ID:
mobile-android-day-13-keystore-misuse - Prompt: "Recover data protected by an app-controlled wrapping key despite nominal Keystore use."
What we were given
- One Android APK per case. Inside:
AndroidManifest.xml,classes.dex,assets/huntress_puzzle.json, andMETA-INF/signing files. - Single Solve:
keystore_misuse.apk, caseMOB-13-BECFE8C675(12,704 bytes, SHA-25680795a1f9f632902e482185f75749f56b7a7a8e39b3bad590bbeb697e021c448). Its puzzle is saved assingle-solve/huntress_puzzle.json. - Time Trial: one APK (case
MOB-13-7652CE7CBF). Mastery: five APKs. These APKs were not saved in the repo.
What was asked
- One question per case: return the exact backend answer code for that case.
- Answer format:
ANS-plus exactly 16 uppercase hex characters. - Answer IDs:
answerfor Single Solve and Time Trial.set1.answertoset5.answerfor Mastery. - New in Mastery: the five cases now mix in older days. They come from Days 2, 5, 8, 10 and 13 (
MOB-02-4A8CDE272E,MOB-05-0C08DB4891,MOB-08-FA0B0E5002,MOB-10-E00023A1B6,MOB-13-CBEBBAEE02). So one run can meet several codecs.
How it was solved, start to finish
The app was never installed or run.
- Started the Single Solve and downloaded the APK.
- Read the puzzle asset. The codec is
base64.
{"schema":"huntress.mobile.puzzle.v1","day":13,"codec":"base64","data":"QU5TLTc3Mzc2MkU4NTc5NzA2NEM="}
- Decoded it:
import json, base64
p = json.load(open('single-solve/huntress_puzzle.json'))
print(base64.b64decode(p['data']).decode())
Output: ANS-773762E85797064C.
- Ran the lane driver for all three modes:
python3 -I ~/.config/huntress/solvers/run_mode.py mobile-android-day-13-keystore-misuse <mode> mobile_puzzle <workdir>
The driver picks the decoder from each APK's own codec field, so a mixed Mastery set works the same way.
- Results: Single Solve (
ANS-773762E85797064C), Time Trial (ANS-D5B50F331B9FF35F) and all five Mastery answers came backCORRECT.
Results
| Mode | Result | Flag |
|---|---|---|
| Single Solve | CORRECT | f26064b81339f0d01a757e87d6e110ba |
| Time Trial | CORRECT | 3aee54eed12b7e86f98828ae4605f1a9 |
| Mastery | CORRECT | af95b5bc49ea89bd0eb55463f26e5a34 |
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-13-keystore-misuse single_solve mobile_puzzle /tmp/d13
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 13: Zip Code
Lane: Script analysis. Modes: Single Solve, Time Trial, Mastery. Result: all CORRECT.
The challenge
- ID:
script-analysis-day-13-archive-delivery-chain - Prompt: "A delivery archive nests scripts inside containers inside more containers. Trace each member's role and handoff without executing a single one, and identify the link in the chain that was never supposed to be delivered."
What we were given
- One
evidence.zip(98,779 bytes, SHA-25608092cc83956b363d385540b735de4538e9e0d230cade07e8a53f9e4598d7ba2). Password:infected. - The same families as Day 12. New today:
- 4 AppleScript polyglots:
polyglot-applescript-benign-utility.applescript,-downloader,-launcher,-staged-chain. - 2 more advanced Bash files:
process-substitution.sh,subshell-pipeline.sh. - Every host and polyglot file carries the
HUNTRESS_ANALYSIS_V1:<ENC>-<data>marker fromDay 8.
What was asked
- 913 questions in Single Solve. By family: PowerShell 15, JScript 72, Batch 72, VBScript 72, Python 126, Bash 126, Node.js 56, host 66, polyglot 308.
- The question types are the same as before. Host and polyglot files get 11 questions each (role, ATT&CK, adapter, campaign, URL or path, host profile, obfuscation, stage profile, next language, stage count, steps).
- Time Trial: 913 questions. Mastery: 4,565 questions in 5 sets.
How it was solved, start to finish
- Started the untimed Single Solve and downloaded
evidence.zip. Extracted it with7z x -pinfected. - Ran the existing solver (
solve_expansion.py, driven byrun_expansion.py). Each family has its own decoder:
| Family | Files | How the config is recovered | First seen | |
|---|---|---|---|---|
| PowerShell | *-sample.ps1 | Base64 JSON inside FromBase64String('...') | Day 1 | |
| JScript | *.js | jsdec.js loads the fixture in a Node vm sandbox (pure-computation globals only) and calls its decode functions | Day 3 | |
| Batch | *.bat, *.cmd | joins the :HUNTRESS_INSPECT fragments and drops ^ carets | Day 3 | |
| VBScript | *.vbs | Material_ + Codec_, transform search until the text starts `v=1\ | steps=` | Day 4 |
| Python | *.py | MATERIAL_ read with ast.literal_eval, same transform search | Day 5 | |
| Bash | *.sh | quoted Material_ + Codec_; "advanced" files start `v=1\ | feature=` | Day 6, Day 7 |
| Node.js | node-*.mjs | Material_ + Codec_ with \x, \u and hex-array formats | Day 7 | |
| host, polyglot | host-*, 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.
- No new code was needed. The prompt talks about nested containers, but every question points at a file at the top of
evidence.zip(for exampleevidence.zip -> array-slicing.sh). A normal 7z extract found every file.
- Ran
run_expansion.pyfor all three modes in one loop. All three came backCORRECT.
- Real answers from
single-solve/answers.json:
{
"polyglot-applescript-downloader-role": "downloader",
"polyglot-applescript-downloader-attack": "T1105",
"polyglot-applescript-downloader-adapter": "http_client",
"polyglot-applescript-downloader-campaign": "APPLESCRIPT-a810b5b7",
"polyglot-applescript-downloader-url": "https://applescript-a810b5b73c.example.invalid/stage",
"polyglot-applescript-downloader-stage-count": "3",
"polyglot-applescript-downloader-steps": "decode_embedded>write_file>dispatch_process",
"polyglot-applescript-downloader-host-profile": "standalone"
}
- Time Trial and Mastery used the same solver on fresh variants.
- Time Trial: 913 questions, no deadline (
run_for_time: false). - Mastery: 4,565 questions in 5 sets, no deadline (
run_for_time: false). The download (script-analysis-day-13-archive-delivery-chain-mastery.zip) holds one inner zip per set. The driver solves each set and adds thesetN.prefix. - Both came back
CORRECT.
Results
| Mode | Result | Flag |
|---|---|---|
| Single Solve | CORRECT | b93ebbecd3882cec00667c7166a5b967 |
| Time Trial | CORRECT | 60bf2b5e7109969e83ec4e4c0745e8ad |
| Mastery | CORRECT | ab97797d67c83aac1406317a40f5a7f2 |
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/d13/ex
7z x -pinfected -o/tmp/d13/ex evidence.zip
python3 -I tools/solve_expansion.py /tmp/d13/ex start-response.json /tmp/d13/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 13: Opposite Day
Lane: Warmups. Modes: Single Solve, Time Trial, Mastery. Result: all CORRECT.
The challenge
- ID:
warmups-day-13 - Prompt: "Mirror, mirror, in the alphabet. Swap the first with the last."
- New encoding: atbash cipher
What we were given
- One blob file per mode (Single Solve and Time Trial), or a zip of multiple blobs (Mastery).
- Each blob has numbered lines (
NN<TAB>fragment). Each line is independently encoded. - The decoded text ends with a slug like
word-word-word-NNto submit.
How it was solved
- Decode the blob. Letter substitution: A maps to Z, B to Y, and so on. Apply the same mapping to decode.
- Mastery blobs use multiple encodings from Days 1-13. The solver (
warmup_decode.py) tries every known decoder on each line and picks the one producing printable text. - Concatenate all decoded lines. The text contains a message ending in the answer slug.
- Submit the slug to the Game Master.
Results
- Single Solve:
CORRECT. slug:handy-candle-quartz-31. Flag:99c0e074550e375f4d3b18e9b0952e0a. - Time Trial:
CORRECT. slug:brave-rainbow-grove-74. Flag:bc130e218d20821033741574c99944e0. - Mastery:
CORRECT. 63 slugs. Flag:547ad27510f60118960459385d2b5b1e.