Portable Executable Format
Also called PE format, PE.
The Windows file format for executables, DLLs, and drivers.
What it is
The Portable Executable format is the structure Windows uses for executables and libraries. It defines headers, a section table, import and export directories, and the layout the loader uses to map the file into memory.
Why it matters
Almost every Windows malware triage starts by parsing the PE: its sections, imports, timestamps, and overlay reveal capability and tampering. Anomalies in the header are themselves strong indicators.
In practice
Spotting a PE whose declared section sizes do not match the file on disk, hinting at a manually mapped payload.
What to look for
- Headers, sections, imports and the compile timestamp.
- Mismatched or missing digital signatures.
- Overlay data appended after the last section.
Common mistake
Trusting the compile timestamp. It is easy to forge, so treat it as a hint.
Use it in CyberKit
In the field
Well-known tools where this shows up on the job. They are listed to show the landscape, not as a recommendation.
-
Ghidra Open source
A disassembler and decompiler for reading what a sample's code actually does. Our notes.
-
YARA Open source
Writes rules that match a family's code or strings across many files. Our notes.
-
VirusTotal Commercial
Shows how many engines flag a file, plus its relations to domains and other samples.
-
ANY.RUN Commercial
An interactive sandbox where you watch a sample run and click through what it asks for.
Tools practitioners use
- PEStudio: Static PE triage & malware indicators
Read next
- PE Section: A named region of a PE holding code, data, or resources.
- Import Address Table: The table the loader fills with addresses of imported functions.
- String Analysis: Extracting readable text from a binary to infer its purpose.