Closed jpbarraca closed 4 years ago
There are a lot of challenges to the VM detection, but I agree that a stronger detection mechanism is needed. For example, checking specific instructions (for example MMX registries presence) or particular IO ports may be feasible. I think that there are a lot of libraries for this :-)
(more info: https://www.cyberbit.com/blog/endpoint-security/anti-vm-and-anti-sandbox-explained/ or Google)
SEB 3.x implements improvements in VM detection, but some of the new code introduced false positives. We close this issue for now, you can create a new one for SEB 3.0 (seb-win-refactoring repository) if you think the improvements are not sufficient.
why? do you want to ruin it for millions of people?
Describe the Bug The Virtual Machine detection function tries to determine if the software is running on a host with some "blacklisted" Manufacturers and Models (VMWare, Virtualbox,...). However this verification is fragile as these strings can be changed in the virtualizer, or additional products can be used (ex, QEMU). This allows running SEB on a VM, easily bypassing the VM detection function.
Steps to Reproduce Steps to reproduce the behavior:
Expected Behavior SEB should detect that it is running on a VM and an error message should be provided.
Screenshots
Version Information