Whats My Name Again? (Day 11, metadata-forensics)
Summary
Filenames on disk are randomized; the organiser's own prompt is explicit that the recovery comes from the Windows PE VERSION_INFO resource instead. This attempt's delivery is one PE file, on disk as telemetry-agent-001.exe (challenge artifact, not published), whose embedded VS_VERSION_INFO -> StringFileInfo -> OriginalFilename field reads pe-base-386.exe (challenge artifact, not published) - the impersonator the prompt asks to expose: the file calling itself telemetry-agent-001.exe (challenge artifact, not published) on disk is, by its own internal record, pe-base-386.exe (challenge artifact, not published).
Gap found and fixed same day
autosolve_metadata.py had no handler for the pe.version_original_filename field token; the first autosolve attempt raised ValueError: unknown structured field 'pe.version_original_filename'. A new extractor, challenges/_lib/pe_version.py, was added and registered in autosolve_metadata.py: it walks the PE resource directory to the VS_VERSION_INFO resource, parses the fixed VS_FIXEDFILEINFO block and the StringFileInfo table, and exposes every standard VERSION_INFO string key (OriginalFilename, InternalName, ProductName, CompanyName, FileDescription, FileVersion, ProductVersion, etc.) under both the exact GM token spelling and the natural synonym spellings a future question could use. The fix cost under a second of agent time; the three modes solved immediately after.
Results - all three modes CORRECT
- Single Solve: Token0e7262929537c2a3aa207d0eb5ff37de (autosolve, 1.6 s, after the pe_version.py fix).
- Time Trial: Tokena994d84bf7688e3056585314bf3fcc76 (2026-10-11T13:01:07.817Z, untimed fallback, 1.5 s).
- Mastery: Tokenf09afecd46d3e9e704e8d920818d3e86 (2026-10-11T13:01:09.206Z, untimed fallback, 1.7 s).
Notes
[gap]lesson recorded same day: a new PE VERSION_INFO string-resource family, now a prepared extractor for any futurepe.version_*field (OriginalFilename, InternalName, ProductName, CompanyName, FileDescription, FileVersion, ProductVersion and more) instead of a one-off patch.- This is the reference writeup for any future PE identity-recovery / impersonation-style challenge.