Extract protected resources from EXE and DLL files
Static extraction, packed-file emulation and a live x64dbg plugin.
Download · Standalone · x64dbg plugin · Tested versions · Research
I wrote this after tracing VMProtect's Resource Protection across versions 3.3.1 to 3.10.1. It locates the encrypted resource table, recovers its key and writes out the resources. You do not need the original unprotected file or a hardcoded address.
Choose the tool that fits the file you have. All three are Windows x64 builds; no kernel driver or separate Python installation is required.
| Tool | Use it when… | v1.0.0 |
|---|---|---|
| Static extractor | The resource table and encrypted data are already present in the file | Download ZIP |
| Emulator | Startup code needs to unpack the resources first | Download ZIP |
| x64dbg plugin | The program is already loaded under the debugger | Download ZIP |
Release notes, checksums and dependency sources
vmp-resource-extractor.exe protected.exe
vmp-resource-extractor.exe protected.dll --output extracted
The default output is protected.exe.resources beside the input. Use a new output folder for each extraction; existing folders are left alone.
vmp-resource-emulator.exe protected.exe --output extracted
The emulator runs the protected startup code in Unicorn until the resources become available. It does not launch the file as a Windows process. Python, Unicorn and Capstone are bundled in the executable.
Emulation limits and larger files
The default limits are 240 seconds and five billion instructions. Increase them when needed:
vmp-resource-emulator.exe protected.dll --seconds 600 --instructions 15000000000
An unsupported API or exception can still stop emulation. The emulation notes list the three packed test files, timings and implementation details.
- Copy
VMPResourceExtractor.dp64into thepluginsfolder besidex64dbg.exe, then start the debugger. - Load the program and let it finish unpacking. For a DLL, wait until its host has loaded and initialized it.
- Open Plugins → VMP Resource Extractor → Extract resources… Select the module and click Scan.
- Choose a new output folder and click Extract. If several tables were found, select one first.
Scan pauses a running target and leaves it paused. Press F9 to continue. Scan again after resuming execution or loading/unloading a DLL.
Refresh updates the module list. Browse picks a parent directory and suggests a new output folder. The plugin reads memory without changing your code or breakpoint settings.
Command-bar usage
vre_ui
vre_scan
vre_extract "C:\work\extracted"
vre_dump "C:\work\extracted-next"
vre_status
vre_dump scans and extracts in one command. See plugin commands and capture limits for module selection, scripting and table selection.
extracted/
├── manifest.json
├── resource-0001.bin
├── resource-0002.bin
└── …
manifest.json records each resource's type, name or ID, language, codepage, size and RVA. The .bin files contain the raw resource bytes: a dialog remains a binary dialog resource, and an icon is not automatically converted to an ICO file.
The input file stays unchanged. This tool extracts the encrypted resource tree; it does not rebuild .rsrc or produce an unpacked executable. Ordinary PE resources outside that tree, such as an unencrypted manifest, are not exported.
| VMProtect | Static x64 EXE / DLL | Live x64dbg extraction |
|---|---|---|
| 3.3.1 | Verified | Verified |
| 3.4.0 | Verified | Verified |
| 3.5.0 | Verified | Verified |
| 3.6.0 | Verified | Verified |
| 3.8.0 | Verified | Verified |
| 3.9.4 | Verified | Verified |
| 3.10.1 | Verified | Verified |
Static and mapped-image tests recovered 126 resources from 21 files, byte-for-byte identical to the originals. Live extraction was checked on every version above.
Real protected x32 files have not been tested. The emulator and plugin currently support x64 only.
Test scope
The 21 files had only Resource Protection enabled. They cover menus, dialogs, string tables, custom types, named resources and multiple languages.
Packed-file emulation was tested separately on the three files documented in the emulation notes. Those tests do not establish support for every packing configuration.
Requirements and build commands
Install Visual Studio C++ Build Tools and the Windows SDK, then run:
.\build.cmd
.\build-plugin.cmd "C:\path\to\pluginsdk"The binaries go into dist. Build instructions cover the emulator, dependencies and tests.
Report a bug with the extraction mode, VMProtect version, protection options and error output.
Ivan Kozlovsky · Website · Email · PGP
Project code: MIT. Bundled dependencies retain their own licenses, including GPL-2.0 for Unicorn. See third-party notices.

