Individual skill

devirtualizing-vm-protected-code

Recover the original logic from code protected by a virtualization obfuscator — VMProtect, Themida/WinLicense, Code Virtualizer, or a custom opcode VM — by locating the VM dispatcher, reverse-engineering the handlers into semantics, extracting the virtual bytecode, and lifting it to a simplified IR with Triton, miasm, or VTIL-based tools. Use when a function became a giant fetch-decode-dispatch loop, when analysis shows a handler table instead of normal code, or after unpacking reveals a virtualized core.

secskills-core/skills/devirtualizing-vm-protected-code/SKILL.md

Read pinned source

Source commit ca53957bcd8e3b83b5d4d190bb3ad008a4f15c84

What was checked

Matches the observed repository HEAD: Yes
Scanner rules are current: Yes
Repository scan complete: No
Skill scan complete: Yes
Observed behavior: Instructions only
Last checked: Nov 11, 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

SKILL.mdcore · 6,403 bytes

Read excerpt


# Devirtualizing VM-Protected Code

Virtualization obfuscation replaces native instructions with bytecode for a
custom virtual machine embedded in the binary, then runs that bytecode through
an interpreter. The original logic is not gone — it is expressed in an
instruction set you have to recover first. Devirtualization is a fixed pipeline:
find the VM, understand its handlers, extract the bytecode, and lift it back to
something readable. The obfuscator changes every build, so the pipeline, not any
one tool, is the durable skill.

## When to Use

- A function turned into a large `fetch-decode-dispatch` loop with a handler
  table instead of ordinary control flow