VMAware (VM + Aware) is a cross-platform C++ library for virtual machine detection.

The library is:

• Very easy to use, with only 5 functions in its public interface
• Very flexible, with total fine-grained control over which techniques get executed
• Cross-platform (Windows + MacOS + Linux)
• Compatible with ARM architecture
• Header-only
• Available with C++11 and above
• Features up to 70+ unique techniques
• Able to detect VMware, VirtualBox, QEMU, KVM, Parallels, and much more
• Able to detect semi-VM technologies like hypervisors, docker, and wine
• Able to guess the VM brand
• Able to add your own custom VM detection techniques
• Memoized, meaning past results are cached and retrieved if ran again for performance benefits
• Contains separate MIT and GPL-3.0 compliant library header files

IMPORTANT:

The library doesn't guarantee it'll be accurate. If you found a false positive or a false negative then please create an issue with information on what your VM is, what OS you're using, and other relevant details.

#include "vmaware.hpp"
#include <iostream>

int main() {
    if (VM::detect()) {
        std::cout << "Virtual machine detected!" << std::endl;
        std::cout << "VM name: " << VM::brand() << std::endl;
    } else {
        std::cout << "Running in baremetal" << std::endl;
    }
    
    std::cout << "VM certainty: " << (int)VM::percentage() << "%" << std::endl;
}

This project also provides a tiny, but handy CLI tool utilising the full potential of what the library can do. Also, running the CLI as root/admin would give better results.

To install the library, download or copy paste the vmaware.hpp file in the release section to your project. No CMake or shared object linkages are necessary, it's literally that simple.

However, if you want the full project (globally accessible headers with <vmaware.hpp> and the CLI tool), follow these commands:

git clone https://github.com/kernelwernel/VMAware 
cd VMAware

sudo dnf/apt/yum update -y # change this to whatever your distro is
mkdir build
cd build
cmake ..
sudo make install

cmake -S . -B build/ -G "Visual Studio 16 2019"

You can view the full docs here. Trust me, it's not too intimidating ;)

• How does it work?

It utilises a comprehensive list of low-level and high-level anti-VM techniques that gets accounted in a scoring system. The scores for each technique are arbitrarily given, and a threshold must be met to detect if it's running in a VM.

• Who is this library for?

It's designed for security researchers, VM engineers, and pretty much anybody who needs a practical and rock-solid VM detection mechanism in their project. For example, if you're making a VM and you're testing the effectiveness of concealing itself, or if you're a malware analyst and you want to check if your VM environment is good enough to avoid detection.

• Why another VM detection project?

There's already loads of projects that have the same goal such as InviZzzible, pafish and Al-Khaser. But the difference between the aforementioned projects is that they don't provide a programmable interface to interact with the detection mechanisms, on top of having little to no support for non-Windows systems. I wanted the core detection techniques to be accessible programmatically in a cross-platform way for everybody to get something useful out of it rather than providing just a CLI tool like those projects.

• Is it possible to spoof the result?

Yes. There are some techniques that are trivially spoofable, and there's nothing the library can do about it whether it's a deliberate false negative or even a false positive. This is a problem that every VM detection project is facing, which is why the library is trying to test every technique possible to get the best result based on the environment it's running under.

• Can I use this for malware?

This project is not soliciting the development of malware for obvious reasons. Even if you intend to use it for concealment purposes, it'll most likely be flagged by antiviruses anyway and nothing is obfuscated to begin with. Good luck manually obfuscating 5000 lines of C++ code lmfao

• Why GPL 3.0 and MIT?

I would've made it strictly MIT so proprietary software can make use of the library, but some of the techniques employed are from GPL 3.0 projects, and I have no choice but to use the same license for legal reasons. This gave me an idea to make an MIT version without all of the GPL code so it can also be used without forcing your code to be open-source. It should be noted that the MIT version removes 8 techniques, and the lesser the number of mechanisms, the less accurate the overall result might be.

• The tool has many false positives under a Windows 11 host, why?

This is because it is in fact running under a VM. More specifically, Hyper-V might be used by default for every program that's running in Windows 11.

If you have any suggestions, ideas, or any sort of contribution, feel free to ask! I'll be more than happy to discuss. If you want to personally ask something in private, my discord is kr.nl

And if you found this project useful, a star would be appreciated :)

• Check Point Research
• Unprotect Project
• Al-Khaser
• pafish
• Matteo Malvica
• N. Rin, EP_X0FF
• Peter Ferrie, Symantec
• Graham Sutherland, LRQA Nettitude
• Requiem
• Alex
• Marek Knápek
• Vladyslav Miachkov
• (Offensive Security) Danny Quist
• (Offensive Security) Val Smith

I am not responsible nor liable for any damage you cause through any malicious usage of this project.

License: GPL-3.0