Series
Investigating PE files
6 posts in this series. Read them in order or jump to any one.
- Detecting Packed Executables: UPX, Entropy and Other Signs
Static signs that a Windows executable is packed or protected — section names, entropy, W+X sections, entry point, imports, overlay — and their pitfalls.
- How to Collect Suspicious Executables Safely
Find and copy suspicious EXE, DLL and SYS files from a Windows host or image without running them: PowerShell, Velociraptor, disk images and pitfalls.
- Analyze an EXE or DLL in Your Browser, Without Running It
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.
- Cobalt Strike Beacon Config: What It Tells Responders
Extract a Cobalt Strike beacon configuration statically and turn each field — C2, sleep, pipe names, spawn-to, watermark, public key — into a hunt.
- Recovering Stack Strings and Decoded Strings in Malware
Why malware hides its strings, how stack strings, tight strings and decoded strings work, and how emulation recovers them without running the file.
- From a PE File to IOCs: MISP, STIX 2.1 and a YARA Draft
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.