Tactical LogHuntress CTF 2026 // team archive

Days / Day 08 / Metadata Forensics / Whats in the Box

DAY 08//LANE: METADATA FORENSICS//STATUS: CORRECT x3

Whats in the Box

SSTTMM Modes reported CORRECT in this write-up

Challenge

  • Category / lane: Metadata Forensics (Huntress CTF 2026, Day 08)
  • GM id: metadata-forensics-day-08-whats-in-the-box
  • Prompt: "The count was only the beginning. Inventory every stored path, preserve directory context, and identify the archive whose names reveal an impossible provenance claim."
  • Modes: Single Solve, Time Trial, Mastery
  • Answers are submitted as per-field answer_ids through the Game Master; flags are returned by the GM on a correct submission.

This challenge extends the Day 02-07 metadata-forensics lane with one new layer: ZIP end-of-central-directory inspection (zip.eocd_total_entries and zip.central_directory_member_names), including an archive nested inside the bundle.

Artifacts

  • metadata-day-08-evidence.zip (challenge artifact, not published) (3308 bytes, sha256 12f42a7fcd717ee6105698873b38b6144ac698b7a6a145dbb2c0a5af7110c9c6) - the Single Solve bundle, saved in this folder.

Bundle members (central directory order):

evidence-note.txt
camera-001.jpg
panel-001.png
document-001.pdf
evidence-drop-001.zip   (nested archive)

Triage

File-type-driven metadata extraction, one field per answer_id. The only new work over prior days is the nested ZIP: parse its End Of Central Directory record for the total entry count and list its central-directory member names in stored order. The themed "impossible provenance claim" is the first evidence note's content, whose first 16 bytes decode to ASCII Case A9706EAF1E5.

Investigation

All values derived from the real downloaded bytes (never retyped):

evidence-note.txt

  • filename: evidence-note.txt
  • size: 33 bytes
  • MD5: cd836b3a174d0ab06510b15c8a9877a0
  • SHA-1: 44afd711074d6af55f5f3c17766a71322993d036
  • SHA-256: 017617c9fe59ab6cc5fab5a6672ca02b7d12b09988a429e022654451d84b1a40
  • first 16 bytes (hex): 43617365204139373036454146314535
  • UTF-8 BOM present: false

image / document headers

  • camera-001.jpg JPEG SOF dimensions: 257x146
  • panel-001.png PNG IHDR dimensions: 269x153
  • document-001.pdf header version: %PDF-1.4

nested archive evidence-drop-001.zip (the new layer)

  • EOCD total entries: 2
  • central-directory member names (compact JSON, stored order): ["room-01/item-1.txt","room-02/item-1.txt"]

The single-solve values were produced by the lane adapter challenges/_lib/autosolve_metadata.py (extended this day for zip.central_directory_member_names) and cross-checked by the derivation script in scripts/.

Flag Recovery

The Game Master validates each mode's per-field answers and returns a completion flag. Verified via op=status for each mode (solved_by Blandman3):

  • single_solve - CORRECT @ 2026-10-08T13:01:16Z
  • time_trial - CORRECT @ 2026-10-08T13:23:52Z
  • mastery - CORRECT @ 2026-10-08T13:23:53Z

The Time Trial / Mastery start route returned HTTP 503 training_rotation_invalid for roughly the first 25 minutes after release (the limited timed Hall-of-Fame rotation pool, affecting multiple lanes event-wide, not our solver). Completing a mode does not require the ranked timed rotation - regular play completes it - and the timed pool recovered by 13:23Z, at which point both timed modes were accepted.

Flag

  • single_solve Token0ab8ac7679c1a5f32c7bf39420316565
  • time_trial Token3adcfffcd7df56efb4cfdfecd9d15602
  • mastery Token9bb1953a6aca9aaea7c9f4994def3b36

Minimal Reproduction

import zipfile, io, hashlib, struct
z = zipfile.ZipFile('metadata-day-08-evidence.zip')
b = z.read('evidence-note.txt')
len(b), hashlib.md5(b).hexdigest(), b[:16].hex(), b[:3] == b'\xef\xbb\xbf'
iz = zipfile.ZipFile(io.BytesIO(z.read('evidence-drop-001.zip')))
len(iz.infolist()), iz.namelist()          # EOCD total entries, member names

Submit each value under its answer_id via the Game Master (op=submit, challenge metadata-forensics-day-08-whats-in-the-box).

Lessons Learned

  • training_rotation_invalid 503 is the timed ranked rotation pool, a separate dual-pool route (run_for_time:true) from regular play. Per the GM openapi/guidance a mode is still completable via regular untimed play / op=practice - do not treat the 503 as "unsolvable", and do not hammer start on a shared timer.
  • op=status is read-only and reports the current result/flag per mode - the cheapest way to learn a mode is already solved (ours showed all three CORRECT once the rotation recovered) and to reconcile a stale local board against GM ground truth.
  • The new layer was exactly one step over Day 07 (nested-ZIP EOCD/central-directory inventory); the banked metadata adapter handled the rest.