Tactical LogHuntress CTF 2026 // team archive

Days / Day 16 / Metadata Forensics / Return to Sender

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

Return to Sender

SSTTMM Modes reported CORRECT in this write-up

Return to Sender (Day 16, metadata-forensics)

GM id: metadata-forensics-day-16-return-to-sender

Task

Artifact is a zip holding one RFC 5322 mail, message-001.eml. Question: Determine email.message_id for message-001.eml. Timed modes (Time Trial, Mastery) are the same shape: evidence zips with filename and evidence-note facts.

Solution

  • Unzip the artifact and read the mail headers. The Message-ID header is the answer, taken raw from the bytes with the angle brackets kept (<[email]> in the Single). The Subject/correlation token and the evidence-note text are decoys.
  • Extractor: email.message_id (and email.header_message_id) were added as aliases of the existing eml.message_id extractor in challenges/_lib/autosolve_metadata.py; no new parser needed. AUTOSOLVE then derived every answer from each attempt's own bytes.

Results (GM-accepted)

  • Single Solve: CORRECT, flag Token1783c21f7e23d03cf466847c903c28f5
  • Time Trial: CORRECT, flag Token2d8fbf780074e7464a44f594ffbeb392
  • Mastery: CORRECT, flag Token754302736d3c4de2ecae53c3a438bb1b

Lesson

A new question key ("email.") for a format whose extractor already exists as "eml." only needs an alias; check the registry first.