Devirt (devirt.re) is a binary devirtualization and reverse engineering service for security researchers and malware analysts. Protectors such as VMProtect and Themida hide a program's logic inside a private virtual machine. Devirt follows the protected program as it runs, reconstructs the virtual machine's state and control flow, converts that behavior into native-shaped functions and checks them against the original. Customers choose the output they need: an IDA database, annotated pseudocode, a reverse engineering report, LLVM IR or structured JSON.
flowchart LR
A["Protected<br/>binary"] --> B["Trace the VM<br/>as it runs"]
B --> C["Rebuild state<br/>and control flow"]
C --> D["Native-shaped<br/>functions"]
D --> E["Check against<br/>the original"]
E --> F["Outputs and<br/>coverage ledger"]
Devirt checks recovered code in three ways:
- Solver check. A solver searches for a counterexample within a declared model. UNSAT supports equivalence within that model, SAT identifies a disagreement, and a timeout leaves the comparison unresolved.
- Differential check. Recovered operations are translated to LLVM IR and compared with the original observations and with native execution for selected inputs.
- IDA persistence check. For IDA output, Devirt saves the database and reopens it to confirm that named functions and typed calls persist.
Read more on how Devirt works.
| Service | What it covers |
|---|---|
| VMProtect devirtualization | An IDA database, annotated pseudocode and a coverage ledger for every protected function |
| Themida devirtualization | Limited recovery per file and broader scopes on subscription, with a coverage ledger on every result |
| Enigma Protector devirtualization | Code recovered from the Enigma Protector virtual machine, delivered as an IDA database with a per-function coverage ledger |
| Obsidium devirtualization | Code recovered from the Obsidium virtual CPU, delivered as an IDA database with a per-function coverage ledger |
| Loki VM devirtualization | Analysis for Obfuscator X, Griffin and other Loki derivatives, with a free assessment for every binary |
| JavaScript VM deobfuscation | Malicious scripts, front-end security reviews and research on code you are authorized to analyze |
| Malware analysis service | Isolated analysis of protected or ordinary samples, a behavioral report and a coverage ledger |
| Software reverse engineering | Readable logic and tool-ready outputs for protected and ordinary binaries |
| Protected binary analysis | Recovered logic and five output formats for packed, obfuscated and virtualized executables |
| Anti-cheat driver auditing | Authorized audits of what kernel-level anti-cheat drivers monitor, collect and expose. Devirt never builds cheats. |
| DRM architecture analysis | For rights holders and vendors reviewing their own protection design, and for authorized interoperability and compliance work |
All services: devirt.re/services
| Protection | How it starts |
|---|---|
| VMProtect, Themida, Code Virtualizer | Automated recovery, with eligibility confirmed for each exact build |
| Enigma Protector, Obsidium | A free assessment of every file, then a written offer |
| Loki-based virtual machines (including Obfuscator X and Griffin) | A free assessment of every binary, then a written offer |
| JavaScript virtual machines, .NET virtualizers, commercial packers, custom virtual machines | A free assessment of every file, then a written offer |
Devirt also analyzes ordinary, unprotected binaries. The current list is on devirt.re/supported-protectors.
| Output | Who it is for |
|---|---|
| IDA database | Analysts who continue in IDA with named functions and typed calls |
| Annotated pseudocode | Readers who need the recovered logic without a disassembler |
| Reverse engineering report | Readers who need conclusions rather than code |
| LLVM IR | Compilers and analysis pipelines |
| Structured JSON | Automation and internal tooling |
Every recovery comes with a coverage ledger. It lists the code in scope and gives each function one of four outcomes, so analysts can see exactly where the evidence stops.
How to read a coverage figure: devirt.re/research/devirtualization/coverage-is-a-contract
| Team | Typical work |
|---|---|
| Reverse engineering consultancies | Outsourcing the devirtualization when VM-protected functions stall a client engagement |
| Malware analysts | Recovering the logic that VM-protected malware hides from the decompiler |
| Vulnerability researchers | Security research on VMProtect- or Themida-protected software within an authorized scope |
| Software owners | Recovering readable logic from a protected binary they own when the source is lost |
| Interoperability teams | Recovering the protocol or file format a protected component hides |
| Supply-chain security teams | Seeing what a vendor's protected code does, beyond a list of components |
| Trust and safety teams | Triage of protected uploaded executables, with the analysis bounds stated |
All use cases: devirt.re/use-cases
- Browser check: reads a file's format and signs of protection on the device, without uploading it.
- Community Triage: a file inventory and protection indicators for a verified account.
- Feasibility assessment: a written scope, estimated coverage and quote for a complex file. Paid work begins only after the customer approves it. See a sample assessment.
Devirt accepts PE, ELF and Mach-O files up to 500 MiB through its web workspace or a REST API with job status and webhooks. Prices are on devirt.re/pricing.
- Devirtualization methods: five method families, from handler analysis to LLVM lifting, and what each can prove
- VMProtect research: how virtualization, mutation and Ultra mode work
- Themida research: how its virtual machines work and why antivirus tools flag protected files
- Binary analysis research: static and dynamic analysis, and what protection hides
- Runtime-dependent, unresolved and bounded functions explained
- Protected binary analysis workflow
What is binary devirtualization?
Protectors such as VMProtect and Themida replace a program's original instructions with bytecode that only the protector's own interpreter understands, so a disassembler or decompiler shows the interpreter instead of the program. Binary devirtualization recovers the logic that the virtual machine hides and turns it back into native-shaped functions an analyst can read.
Is Devirt related to compiler devirtualization?
No. Devirt (devirt.re) is not related to compiler devirtualization, the C++ optimization in GCC and LLVM that replaces virtual function calls with direct calls.
Does Devirt return the original source code?
No. Devirt returns inspectable logic, not the original source code, and a verified result applies to the declared scope and inputs rather than to every possible behavior of the program.
Which files can Devirt analyze?
Devirt only analyzes software that customers own or are authorized to examine, and it may decline a job or ask for clarification of scope or authorization. Eligibility is confirmed for each exact build, because a protector's name does not prove that a file can be recovered.
What happens to uploaded files?
Devirt processes each file in isolation and does not use customer files for model training. Input files are deleted after delivery.
Website · YouTube · Knowledge base · Notion · Medium · DEV Community · SourceForge · Devpost · Quora · Gravatar · Bluesky · Mastodon · Reddit · Hacker News · Buttondown · Quora Space · Contact
Devirt only analyzes software that customers own or are authorized to examine.