Tactical LogHuntress CTF 2026 // team archive

Days / Day 03 / Metadata Forensics / BOM Voyage

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

BOM Voyage

SSTTMM Modes reported CORRECT in this write-up

Lane: Metadata Forensics (Day 03). GM id metadata-forensics-day-03-bom-voyage.

Challenge

Text export files "look identical in an editor but behave differently in scripts." Each answer is text.utf8_bom_present (enum true/false) for a file inside the assigned zip.

Investigation

  • Answer is a pure function of the file's first 3 bytes: EF BB BF -> true, else false.
  • Single Solve and Time Trial: one zip, one file; false accepted both times (roster/evidence-note had no BOM).
  • Mastery: two zips; the questions text (file names, ids) is a DECOY - use answer_ids (setN.<id>) and map set N to download N-1. set1 file started with BOM (true), set2 did not (false).
  • Gotchas: pyzipper absent on VM (zips are plain deflate; use zipfile); Mastery deadline is short, so run start->download->submit in one script (solve_mastery.py).

Flags (completion tokens)

  • single_solve Token78f82e05467dd5acd015e6915449d36c
  • time_trial Token4c622376f768e732581091661f06c428
  • mastery Tokenedd681e696d84c4416d62690a66b7a68

Minimal Reproduction

scp ctf_gm.py solve.py solve_mastery.py to the VM; python3 solve.py, python3 solve.py /time_trial, python3 solve_mastery.py.

Lessons

Trust answer_ids over questions text in Mastery; check magic bytes directly.