Tactical LogHuntress CTF 2026 // team archive

Days / Day 09 / Metadata Forensics / Built Different

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

Built Different

SSTTMM Modes reported CORRECT in this write-up

Challenge

  • Category: Metadata Forensics (Day 09). Game Master ID metadata-forensics-day-09-built-different.
  • Prompt: "A software drop contains executables for several architectures, plus decoys wearing executable extensions. Determine what can actually run where."
  • Modes: Single Solve, Time Trial, Mastery - all CORRECT (3/3).
  • Answer form: 13 per-field answers derived from the assigned bytes (filename, size, md5/sha1/sha256, and format/arch facts). No flag{} wrapper; the GM returns a completion token per mode.

Artifacts

  • evidence.zip (challenge artifact, not published) assigned per attempt by the Game Master (dynamic; analysed from the attempt's own bytes).

Triage

Metadata-bytes family (see docs memory ctf-evidence-note-decoy-family): every answer is a function of the assigned file's raw bytes, and extensions are untrusted - the drop mixes real executables for several architectures with decoys that merely wear an executable extension. File magic, not extension, decides what can actually run where.

Investigation

Solved by the generic adapter challenges/_lib/autosolve_metadata.py at claim time: it reads each named member of evidence.zip (challenge artifact, not published), hashes it (md5/sha1/sha256), records the true size, and derives the format/architecture from magic bytes rather than the extension. The 13 answer fields were produced directly from those bytes; the decoy "executables" are identified by their real magic.

Flags (GM completion tokens, per mode)

  • single_solve Token6b2dd52062df8227495b93c350bd2f5f
  • time_trial Tokenb7206fe8221771f3467096069feebcca
  • mastery Tokenc633079e248f2b1b9dc3ba7a60e7b587

Minimal Reproduction

wsl python3 challenges/_lib/autosolve.py 9 metadata-forensics-day-09-built-different metadata-forensics - start, download the attempt's zip, hash + identify each member by magic, submit the 13 fields.

Lessons Learned

  • Extension is a decoy signal; identify "what can run where" from magic bytes. The metadata adapter already does this, so all three modes auto-solved with no model reasoning.