Tactical LogHuntress CTF 2026 // team archive

Days / Day 20 / Metadata Forensics / Universal Appeal

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

Universal Appeal

SSTTMM Modes reported CORRECT in this write-up

Universal Appeal (Day 20, metadata-forensics)

GM id: metadata-forensics-day-20-universal-appeal. Question: Determine macho.cpu_type_set for macos-001.bin (answer kind json: compact JSON array).

Single Solve - CORRECT

  • Flag: Token29f836971748707c3e26a94cab556c38
  • artifact_0.bin is a zip with one member, macos-001.bin (challenge artifact, not published) (56 bytes): a thin little-endian 64-bit Mach-O (cffaedfe), cputype bytes 0c000001 = 0x0100000c (arm64), one LC_UUID command.
  • Answer-format search (the GM never says the element spelling): bare 0x100000c wrong, ["arm64"] wrong, [16777228] wrong, ["ARM64"] wrong, ["0x0100000c"] CORRECT.
  • Accepted form: a compact JSON array of 8-digit lowercase hex strings with 0x prefix, unique CPU types in slice order, e.g. ["0x0100000c"] (fat files: ["0x0100000c","0x01000007"]).
  • Fix: challenges/_lib/hdr_facts.py now emits macho.cpu_type_set (thin and fat; fat uses each slice's own header cputype, falling back to the fat arch record).

Time Trial - CORRECT

  • Flag: Tokena75f247e7bd0149b4991f4291b22b6ec
  • First ranked autosolve pass HELD because the roster-filename question had no extractor (no sibling question names the roster), which spent the timed window (GM: finished, 0 variants, next_op practice).
  • Added to autosolve_metadata.py: when a filename question mentions the roster and no sibling names it, answer with the one zip member whose base name starts with roster. Offline test: Day 20/Universal Appeal/scripts/test_extractors.py.
  • The client refused the documented untimed practice write (one timed write per gate pass); the user ran autosolve once with the named Commander override (challenges/tt.sh), practice completed the mode.

Mastery - CORRECT (ranked)

  • Flag: Token84b48cf2af3e64b8e55f8a38d995af28
  • Solved by the same autosolve pass, 3.8 s, after Time Trial was CORRECT. The renamed-evidence-note-copy question was already handled (same-bytes member under another name).

Lessons

  • Prebrief residue ids on a Single stand-in (roster-filename, copy-filename) must be built BEFORE the first autosolve pass that can open a ranked timed window (hof_on).
  • cpu_type_set element format is hex strings, not names or decimals.