Tactical LogHuntress CTF 2026 // team archive

Days / Day 13 / Metadata Forensics / Product Placement

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

Product Placement

SSTTMM Modes reported CORRECT in this write-up

Product Placement (Day 13, metadata-forensics)

Question: Determine msi.product_code_guid for installer-001.msi.

Method

  • artifact_0.bin is a zip holding installer-001.msi (challenge artifact, not published) (OLE2 compound file).
  • MSI streams use an encoded stream-name alphabet; the Property table is column-major, with string references into _StringPool / _StringData. Parsed these directly (olefile + struct) in challenges/_lib/msi_meta.py.
  • Property table: ProductCode = {[id]}, UpgradeCode = {[id]}, ProductVersion = 1.13.0. SummaryInformation Revision Number (package code) is a different GUID and is not the product code.

Answer format (important)

The GM rejected plain lowercase and plain uppercase GUIDs. It accepted the MSI-native braced uppercase form:

{[id]}

Single Solve flag: Token4020c4ef38b46c4267843486a811ee1a

Timed modes

Extractor registered in autosolve_metadata.py (msi_meta.register). AUTOSOLVE solved Time Trial and Mastery (CORRECT).

Lesson

Pattern text "8-4-4-4-12 incl. hyphens" did not mean unbraced; use the native form of the format.