Blog
Guides to Windows PE files for incident responders: headers, imports, signatures, packers and triage.
Extract a Cobalt Strike beacon configuration statically and turn each field — C2, sleep, pipe names, spawn-to, watermark, public key — into a hunt.
Extract indicators of compromise from Windows executables, defang them, filter the noise and export them as CSV, a MISP event, a STIX 2.1 bundle or a YARA rule.
Why malware hides its strings, how stack strings, tight strings and decoded strings work, and how emulation recovers them without running the file.
Step-by-step static triage of Windows executables with the free PE Parser: load files or a ZIP, read indicators, compare builds and export results.
Find and copy suspicious EXE, DLL and SYS files from a Windows host or image without running them: PowerShell, Velociraptor, disk images and pitfalls.
Static signs that a Windows executable is packed or protected — section names, entropy, W+X sections, entry point, imports, overlay — and their pitfalls.
Where a Windows executable stores its times, which ones can be trusted, how reproducible builds and timestomping show up, and how to use them.
How Authenticode signs a PE file, which checks can be done from the file alone, and why a valid signature is not the same as a trusted one.
How imphash, the Rich header hash and TLSH group related Windows executables, how each is computed, and where each one breaks down.