Individual skill
unpacking-protected-binaries
Unpack and dump protected executables — UPX and commodity packers, custom crypters, commercial protectors like Themida and VMProtect, and .NET packers — by finding the original entry point, dumping from memory, and rebuilding the import table with Scylla, pe-sieve, or x64dbg. Use when a binary has high entropy, few imports, unnamed sections, or when analysis tools show almost no code.
secskills-core/skills/unpacking-protected-binaries/SKILL.md
Source commit ca53957bcd8e3b83b5d4d190bb3ad008a4f15c84
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- No
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Not checked yet
- Last checked
- Nov 6, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 188
- Repository last updated
- Sep 4, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- security Repository topic
- skills Repository topic
- engineering Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
Read excerpt
# Unpacking Protected Binaries
Static unpacking is a trap for anything beyond UPX. The reliable method is to
let the program unpack itself, then take the result out of memory. Almost every
protector, however sophisticated, must eventually produce executable code in a
readable page — that moment is what you are waiting for.
Run protected samples only in a contained environment; see `analyzing-malware`.
## When to Use
- `binwalk -E` shows uniformly high entropy across most of the file
- The import table has a handful of entries (`LoadLibrary`, `GetProcAddress`)
- Section names are absent, random, or `UPX0`/`.themida`/`.vmp0`