Tactical LogHuntress CTF 2026 // team archive

Days / Day 19 / Metadata Forensics / Little Endian on the Prairie

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

Little Endian on the Prairie

SSTTMM Modes reported CORRECT in this write-up

Little Endian on the Prairie (metadata-forensics, Day 19)

GM id: metadata-forensics-day-19-little-endian-on-the-prairie

Task

Question: Determine elf.e_machine_u16_hex for collector-001.elf. Answer shape: lowercase hexadecimal with a 0x prefix, no explanatory text.

Method

  • Artifact is a zip with one member, collector-001.elf (challenge artifact, not published).
  • The answer comes from the ELF header bytes, not from the filename or any note: ELF64 (EI_CLASS=2), little endian (EI_DATA=1), so e_machine is the u16 at offset 0x12, read little endian.
  • Bytes at offset 0x12 give 0x003e (x86-64). Width follows the field type: u16 -> 4 hex digits.
  • Answer: 0x003e.
  • The banked autosolver (challenges/_lib/autosolve_metadata.py, hdr_struct ELF table) derived the same value for all three modes from each attempt's own bytes.

Results (all accepted by the GM)

  • Single Solve: CORRECT, flag Token40f7fe19c7ac8391ce7ec5cca3dc8e29
  • Time Trial: CORRECT, flag Token3b79f3700b81f6c7aea4bcdd6bdd2e80
  • Mastery: CORRECT (ranked), flag Token2afdce6244a357f8236f81302027226f

Notes

  • No new extractor was needed: the ELF field table was already prepared (NEXT-LAYER candidate "elf").
  • Pre-brief gap lines for Time Trial / Mastery (roster-filename, evidence-note-copy-filename) were not hit; the mutated attempts still resolved from the header.