Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

New anti-VM WMI checks #172

Open
gsuberland opened this issue Apr 13, 2019 · 1 comment
Open

New anti-VM WMI checks #172

gsuberland opened this issue Apr 13, 2019 · 1 comment
Assignees

Comments

@gsuberland
Copy link
Collaborator

Based on some experimentation, if these classes have no instances it's a good chance of being a VM:

Win32_CacheMemory, Win32_PhysicalMemory,
Win32_MemoryDevice, Win32_MemoryArray, Win32_VoltageProbe,
Win32_PortConnector, Win32_SMBIOSMemory, ThermalZoneInfo performance
counters, CIM_Memory, CIM_Sensor, CIM_NumericSensor,
CIM_TemperatureSensor, CIM_VoltageSensor, CIM_PhysicalConnector, and
CIM_Slot

For VirtualBox I also have some specific WMI detections:

  • Win32_PnPDevice DeviceId values
  • Win32_PnPDevice Name values (common controller devices (82801FB, 82441FX, 82371SB, OpenHCD)
  • Win32_PnPDevice Name values containing VBOX
  • Win32_Bus only having ACPIBus_BUS_0, PCI_BUS_0, PNP_BUS_0
  • Win32_BaseBoard values ("VirtualBox", "Oracle Corporation")
@gsuberland
Copy link
Collaborator Author

I'm not closing this just yet as I think there are more Win32_PnPDevice, Win32_BaseBoard, and Win32_Bus checks to do for other virtualisation platforms.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant