2026-10-01

Day 1: ELF Aware

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

Day 1 was solved by hand with readelf and objdump. These tools only read the file.

  1. Started the attempt and downloaded the zip. Unzipped it with unzip -oq evidence.zip -d files.
  2. Read the header and section table with readelf -h -S -sW:
  1. Read the marker with readelf -x .huntress. It holds BR01-SYMBOL-ORIENTATION.
  2. Found the returned constant. objdump -d -M intel --disassemble=recover_code shows mov eax,0x539 then ret. 0x539 is 1337.

Re-checked with a small Python parser (symbol table → function bytes):

recover_code: vaddr=0x401120 size=6 file_off=0x1120 bytes=b8 39 05 00 00 c3
  mov eax, 0x539  -> 1337
  1. Submitted the 9 answers in answers.json. Examples: "elf_type": "ET_EXEC", "marker": "BR01-SYMBOL-ORIENTATION", "recover_code": "1337", "entry_point": "0x401030". Result: CORRECT.
  2. Time Trial:
  1. Mastery:

Results

ModeResultFlag
Single SolveCORRECTf61edda783482ec70bf509132cc25d41
Time TrialCORRECT16883e2891052e3b4cfcb0e25384560c
MasteryCORRECT (practice)3d6d6d0d1cd19d185c436ee82db7c54f

Each mode folder has the zips, the extracted ELF files, the answers, the command output, and the raw Game Master responses. No screenshots were taken.

Reproduce

cd single-solve
unzip -oq evidence.zip -d files
readelf -h -S -sW files/symbol-orientation.elf
readelf -x .huntress files/symbol-orientation.elf
objdump -d -M intel --disassemble=recover_code files/symbol-orientation.elf

These commands only read the file. They never run it.

Day 1: You Must Be This Hash to Ride

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

These were solved by hand with standard command-line tools. Each mode folder has a commands-output.md with the exact commands and output.

  1. Started the attempt. The reply listed the questions. Each question names its file, for example metadata-day-01-evidence.zip -> evidence-note.txt.
  2. Downloaded the zip and listed it with unzip -l to get the exact member names.
  3. Extracted the files. The mastery inner zips were extracted with 7z x -pinfected.
  4. Measured and hashed each named file:
wc -c files/evidence-note.txt
md5sum files/evidence-note.txt
sha1sum files/evidence-note.txt
sha256sum files/evidence-note.txt

Single Solve output:

240 files/evidence-note.txt
6b5074cd2b741ee5d0f0f9cae5eba7d5  files/evidence-note.txt
11f594f647b3c81bce2527c0d9f6c72a60f492d9  files/evidence-note.txt
a6d2d239a6ba996a16ea585c9dd5874b9a0fcdb1e16e3f10457d5ea79e944dc6  files/evidence-note.txt
  1. Checked which labels can be trusted. In the Time Trial zip and in both mastery sets, evidence-note.txt and evidence-note-copy.txt have the same bytes. So the "copy" label is true. roster.csv is a different file with its own hashes.
  2. Submitted every answer under the exact answer IDs from the start reply. Examples from the answer files:
  1. The Game Master replied CORRECT for each mode and returned the flag.

Results

ModeResultFlag
Single SolveCORRECT4079fe133b7df492ee6f974989caec22
Time TrialCORRECT3292cc8f4328d673a49f7d048290e048
MasteryCORRECT3273f32b95bf615f1a0c75ca4630de18

Each mode folder has start-response.json, answers.json, submit-response.json, commands-output.md, the original zip and the extracted files. No screenshots were captured.

Reproduce

cd single-solve
unzip -l metadata-day-01-evidence.zip
wc -c files/evidence-note.txt
md5sum files/evidence-note.txt; sha1sum files/evidence-note.txt; sha256sum files/evidence-note.txt

The same field types are handled later by ~/.config/huntress/solvers/run_meta.py (-filename, -size-bytes, -md5, -sha1, -sha256). Nothing here runs the files; it only reads their bytes.

Day 1: Exported Trust

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. Everything came from the APK bytes.

  1. Started the attempt and downloaded the assigned APK from the Game Master.
  2. Read the manifest with aapt dump xmltree. It shows an exported .ChallengeActivity with a VIEW + BROWSABLE filter for huntress01://exported-trust/unlock.
  3. Read the DEX. ChallengeActivity reads the answer and case_id values and forwards them to the evidence endpoint.
  4. Tried the local backend. The request from the VM got "connection refused". So the code was taken from the answer bundled in the APK instead.
  5. Read the puzzle asset. The codec is plain, so data is already the answer:
unzip -p exported_trust.apk assets/huntress_puzzle.json
{"schema":"huntress.mobile.puzzle.v1","day":1,"codec":"plain","data":"ANS-DACC86F43B0B1C1A"}
  1. Submitted ANS-DACC86F43B0B1C1A under answer. The Game Master replied CORRECT.
  2. Time Trial: downloaded the APK with op=artifact, read the same asset. It gave ANS-2010BA5274DFFAE1.
  3. Mastery: read the asset in each of the three APKs. The codes were ANS-4324FFECDA397A2A, ANS-946ED16E5EC11EF6 and ANS-E4B93CC458BAFB45. All three went in one submit.

Results

ModeResultFlag
Single SolveCORRECT15da3bfcc83a96a7c1bc7f8a7ff79e3d
Time TrialCORRECTd041da5da21c72e69ae6052384192aaf
MasteryCORRECT180a5d968c1d7031f88533a715b5404b

Each mode folder has the APK(s), the extracted puzzle, answers.json, start-response.json, submit-response.json, and a commands-output file with the commands and output. No screenshots were taken.

Reproduce

Offline, from the saved APK:

unzip -p single-solve/exported_trust.apk assets/huntress_puzzle.json

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

python3 -I ~/.config/huntress/solvers/run_mode.py mobile-android-day-01-exported-trust single_solve mobile_puzzle /tmp/d01

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 1 — Read the Rules

Lane: (introductory) · Challenge ID: read-the-rules

> Read the rules page. Find the hidden flag.

What we were given

A link to the CTF rules page at https://ctf.huntress.com/rules.

How it was solved

  1. Downloaded the rules page. It's a Next.js app — the static HTML shell loads a route script.
  2. The route script uses dangerouslySetInnerHTML to inject an HTML comment into the page. The comment contains the flag.
  3. Viewing page source (or inspecting the JS bundle) reveals the flag string.
  4. Submitted the flag to the Game Master.

This is a warmup — the lesson is "always view source."

Results

ModeResult
Single SolveCORRECT

Day 1: Power Play

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 an attempt with the Game Master (op=start). It returned the prompt and the 15 questions as JSON.
  2. Downloaded the artifact and extracted it with 7z. Three files came out.
  3. Read the files as text. Nothing was run.
  4. Decoded each descriptor. A regex finds the Base64 string, then it is decoded and parsed as JSON. This is the exact command from single-solve/commands-output.md:
import base64, json, pathlib, re

for path in pathlib.Path(".").glob("*-sample.ps1"):
    encoded = re.search(r"FromBase64String\('([^']+)'\)", path.read_text()).group(1)
    print(path.name, json.loads(base64.b64decode(encoded)))

Output (Single Solve):

resource-sample.ps1: {"a":"a88bfda72dbe","b":"https://cdn-03ce326948.example.invalid/3e59094b24e2.bin","c":"wallet_d327bc1114a907589af81bba71226b77","d":"update-03ce326948.dat","e":"HKCU\\Software\\HuntressLab\\Run\\03ce326948","f":"Mozilla/5.0 HuntressLab/3.6","g":64,"h":"Global\\HuntressLab_6460b4f6aa72"}
collection-sample.ps1: {"a":"e536c782dd01","b":"https://497b6b9b43.example.invalid/3f890532dd42.dat","c":["update-497b6b9b43.dat","Login Data","Cookies"],"d":"stage-e536c782dd01.zip","e":"Global\\HuntressLab_03b15c606290","f":"Mozilla/5.0 HuntressLab/3.3"}
impact-sample.ps1: {"a":"785244c7fdf5","b":".locked-1d685","c":"RECOVERY-1d6858b777.txt","d":"https://1d6858b777.example.invalid/a0e20204ed17.dat","e":["update-1d6858b777.dat","Login Data","Cookies"],"f":"Global\\HuntressLab_b2e257a4ea0f"}
  1. Picked each indicator by its shape. The key letters move around between files, so the value's form is what matters:
  1. Mapped scenario and ATT&CK by file. A few real answers from single-solve/answers.json:
{"resource-scenario": "resource_hijacking", "resource-attack": "T1496",
 "collection-scenario": "synthetic_collection", "collection-attack": "T1555.003",
 "collection-file": "update-497b6b9b43.dat", "collection-user-agent": "Mozilla/5.0 HuntressLab/3.3",
 "impact-scenario": "synthetic_impact", "impact-attack": "T1486", "impact-note": "RECOVERY-1d6858b777.txt"}
  1. Submitted all 15 answers as one JSON object. The Game Master replied CORRECT and returned the flag.
  2. Time Trial: a new evidence.zip (SHA-256 76980d6a5ad47ff42da017569278ceaf77bc9f226090bd5fa5d947c3caf5480e) with fresh values. The deadline was 50 seconds after the start. Same steps. The decoded values are in time-trial/commands-output.txt.
  3. Mastery: 30 questions in two sets (set1.*, set2.*), with an 80-second deadline. The download was mastery.zip (5,166 bytes, SHA-256 f96ad10b598a63dc897fd8890dd7de8cbbd9cbc1717d3f72627484d057b1b2cd). It holds evidence-01.zip and evidence-02.zip, one per set. Each set was decoded the same way, and the answers were sent under their setN. IDs. See mastery/commands-output.txt.

Results

ModeResultFlag
Single SolveCORRECT8011b2699059fed172501b192bc44e2b
Time TrialCORRECTd89beb994e05ea968d54e417c93b8bed
MasteryCORRECT341deea112be2d8eb47db3825fe2ff98

Each mode folder keeps the archive, the extracted .ps1 files, start-response.json, answers.json and submit-response.json. No screenshots were taken.

Reproduce

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

mkdir -p /tmp/d01/ex
7z x -pinfected -o/tmp/d01/ex repos/day-01-script-analysis-power-play/single-solve/evidence.zip
python3 -I tools/solve_expansion.py /tmp/d01/ex \
  repos/day-01-script-analysis-power-play/single-solve/start-response.json /tmp/d01/answers.json

This rebuilds all 15 saved answers (re-checked on 2026-11-01). The solver only reads the .ps1 files as text.

Day 1: A Little Based

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. Base64-decode the blob to get plaintext.
  2. The decoded text contains a message ending in the answer slug.
  3. Submit the slug to the Game Master.

Results

Day 1 — Welcome Robots

Lane: (introductory) · Challenge ID: welcome-robots

> Ask your AI teammate to identify the Welcome Robots challenge and provide the answer.

What we were given

A prompt asking for the AI teammate's answer.

How it was solved

  1. Queried the Game Master API for the Welcome Robots challenge.
  2. The Game Master returned the flag directly — this was an introductory challenge testing that the AI Arena tooling was working.
  3. Submitted the returned flag.

This is a connectivity/setup check, not a real challenge.

Results

ModeResult
Single SolveCORRECT