Packing
Also called Packer.
Compressing or encrypting a binary to hide its real code.
What it is
Packing wraps an executable in a layer that compresses or encrypts the original code and restores it in memory at runtime. Packers range from common compressors to bespoke crypters.
Why it matters
It defeats static analysis and signature matching by hiding strings and logic until execution, so analysts often must unpack (by running it under control) to see the true behavior.
In practice
A sample whose only readable strings belong to the unpacking stub; its real payload appears only once it runs.
What to look for
- Section names from known packers, or sections that are writable and executable.
- Very few imports, often just enough to unpack.
- A large gap between a section's raw and virtual size.
Common mistake
Writing signatures for the packer instead of the payload. Many legitimate programs use the same packer.
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.
ATT&CK techniques
- T1027.002: Software Packing
Tools practitioners use
- Detect It Easy: File type, packer & compiler identification
Read next
- Entropy: A randomness score that flags packed or encrypted data.
- Sandboxing: Detonating a sample in an isolated environment to watch its behavior.
- Rootkit: Stealth malware that hides itself deep in the OS.