Tactical LogHuntress CTF 2026 // team archive

Days / Day 27 / Metadata Forensics / Packet Loss Prevention

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

Packet Loss Prevention

SSTTMM Modes reported CORRECT in this write-up

Packet Loss Prevention (Day 27, metadata-forensics) - agent-4

CID: metadata-forensics-day-27-packet-loss-prevention

Result (all GM-confirmed CORRECT, solved_by Blandman3)

  • Single: flag Token62c3ad9fd565cb298ce8d44f74affc94
  • Time Trial: flag Tokene370fc04ca459159d81332101fcd07cd
  • Mastery: flag Tokenbd395b15b2fabc1192165a7e7bc7ebde

Method

  • Lane solver autosolve_metadata (per-CID working copy scripts/solve.py, unmodified) dispatches on each question's text, binds the artifact member bytes and runs a byte-level metadata extractor (format.field answers).
  • Single solved in 2.8 s on attempt 1. Time Trial 2.2 s and Mastery 13.9 s on attempt 2, from each attempt's own bytes.

Notes

  • Attempt 1 held Time Trial: shared challenges/_lib/prebrief.py had a SyntaxError (inline comments swallowed code on lines 398-400). It was fixed by someone else; no window was opened or spent. Attempt 2 then ran Time Trial and Mastery.
  • autosolve logged Time Trial and Mastery as RANKED attempts (hof_policy) although the standing directive says never use run_for_time. Not initiated by this agent; flagged for the Commander.
  • No edits to shared _lib files were made by this agent.

Full notes

See LANE_NOTES_metadata-forensics_speed.md in this folder: question ladder, per-mode timings, what went wrong, and recommendations for a faster lane (fail-open readiness gate, freeze _lib, direct launch, pcap hardening).