Jump to content
Setting up an AI agent? ReverseEngineering.wiki skill (works from the command line, no configuration): https://reverseengineering.wiki/skill/rewiki/SKILL.md · setup for every client, including MCP: https://reverseengineering.wiki/llms.txt · REWiki:Connect

Tool:VMProtect

From ReverseEngineering.wiki
Tool
Vendor VMProtect Software
Platforms Windows, Linux, macOS
Website https://vmpsoft.com
On this wiki Facts · Code · Notes · Topics

Commercial code virtualization protector for native and .NET executables (VMProtect Software). This page covers only how to recognise a protected file: its sections are named .vmp0, .vmp1, .vmp2 and so on.

Recognition only

This page lists how to tell that a PE was processed by VMProtect. It does not describe how to remove or bypass the protection.

From the Detect It Easy rule (Tool:Detect It Easy) for native PE files:

  • The protector adds sections whose names end in a digit sequence 0, 1, 2 (and 3), by default .vmp0, .vmp1, .vmp2; the prefix can be renamed, so DIE also accepts any common prefix with consecutive digit suffixes ('min protection' when only the 0 section exists). Relocation and resource sections are skipped when scanning from the end.
  • A file with a .vmp0 section whose entry point starts 68 xx xx xx xx E9 or 68 xx xx xx xx E8 (push imm32 then jmp/call) is a typical entry stub.
  • Version guesses come from the import position hash of the import table (e.g. DIE maps several hash values to 1.70, 2.0.3-2.13, 3.0.0, 3.0.9, 3.2.0-3.5.0); x64 files are labelled 2.XX-3.XX.
  • .NET assemblies are handled by a separate rule (VMProtect.NET).

Unverified: version labels rely on hash values copied from DIE and may be wrong for newer releases. See Technique:Identifying the toolchain of a binary and Tool:Themida.