gitwtfhub

wtf is vmphide?

adofyn1/vmphide — explained in plain English

Analysis updated 2026-05-18

34CAudience · researcherComplexity · 5/5Setup · hard

TL;DR

A reverse engineering tool that helps analysts bypass VMProtect's anti-debug and anti-virtual-machine checks on Windows.

Mindmap

mindmap
  root((VMPHide))
    What it does
      Bypasses anti debug checks
      Bypasses anti VM checks
      Ships driver and plugin
    Tech stack
      C
      Windows driver
      x64dbg
    Use cases
      Analyze protected binaries
      Debug under VMProtect
      Run in a VM undetected
    Audience
      Security researchers
      Reverse engineers

Code map

Detail Auto

An interactive map of this repo's files and how they connect — its source is parsed live in your browser. Click Visualize to build it.

filefunction / class

Why would anyone build with this?

REASON 1

Analyze a VMProtect-protected Windows binary with a debugger attached without triggering its anti-debug checks.

REASON 2

Run VMProtect-protected software inside a virtual machine for analysis without triggering its anti-VM checks.

REASON 3

Use the x64dbg plugin or CLI to apply the anti-debug and anti-VM bypasses during a reverse engineering session.

What's in the stack?

CWindows driverx64dbg

How it stacks up

adofyn1/vmphidedotike/fshdreamfekk/andriod-autouedump-gui
Stars343335
LanguageCCC
Setup difficultyhardmoderatehard
Complexity5/52/55/5
Audienceresearcherdeveloperresearcher

Figures from each repo's GitHub metadata at analysis time.

How do you spin it up?

Difficulty · hard Time to first run · 1h+

README does not document build or install steps, requires familiarity with Windows drivers and x64dbg.

Wtf does this do

VMPHide is a small reverse engineering utility aimed at software protected by VMProtect, a commercial code obfuscation and anti-tamper tool. It works around the checks VMProtect uses to detect whether its protected program is being debugged or is running inside a virtual machine, which is a common step for security researchers analyzing protected binaries. The project ships as three pieces: a Windows driver, a plugin for the popular x64dbg debugger, and a command line tool, so it can be used depending on how someone prefers to work. On the anti-debug side, the README lists the specific detection methods it defeats. These include checks against a process's PEB structure, such as the BeingDebugged flag and the process heap flags, along with several Windows system calls that a debugged process would otherwise expose, like NtQueryInformationProcess calls that reveal a debug port or debug object handle. It also handles a trick involving closing an invalid handle, which crashes a program only if a debugger is attached, and covers the ThreadHideFromDebugger flag that Windows lets a program set to hide a thread from debugging tools. On the anti-VM side, it addresses a CPUID based check, which normally involves changing a virtual machine's configuration file, and a system information query that can reveal firmware details pointing to a virtual machine. The README gives one concrete usage example for the anti-VM case, showing that setting a specific hypervisor CPUID flag to false in a VMware .vmx configuration file is part of how the anti-VM bypass is used. The README is brief and does not describe installation steps, build instructions, or a license, beyond listing the included components and the detection methods it targets.

Yoink these prompts

Prompt 1
Explain what each anti-debug technique VMPHide bypasses actually detects, like PEB.BeingDebugged and ThreadHideFromDebugger.
Prompt 2
How do I load the VMPHide x64dbg plugin and driver to analyze a VMProtect-protected binary?
Prompt 3
Walk me through the .vmx configuration change VMPHide's README mentions for bypassing the anti-VM CPUID check.
Prompt 4
What is the difference between VMPHide's driver, x64dbg plugin, and CLI components?

Frequently asked questions

wtf is vmphide?

A reverse engineering tool that helps analysts bypass VMProtect's anti-debug and anti-virtual-machine checks on Windows.

What language is vmphide written in?

Mainly C. The stack also includes C, Windows driver, x64dbg.

How hard is vmphide to set up?

Setup difficulty is rated hard, with roughly 1h+ to a first successful run.

Who is vmphide for?

Mainly researcher.

View the repo → Decode another repo

This repo across BitVibe Labs

Don't trust strangers blindly. Verify against the repo.