An adversary may attempt to enumerate running virtual machines (VMs) after gaining access to a host or hypervisor. For example, adversaries may enumerate a list of VMs on an ESXi hypervisor using a Hypervisor CLI such as esxcli or vim-cmd (e.g. esxcli vm process list or vim-cmd vmsvc/getallvms).[1][2] Adversaries may also directly leverage a graphical user interface, such as VMware vCenter, in order to view virtual machines on a host.
Adversaries may use the information from Virtual Machine Discovery during discovery to shape follow-on behaviors. Subsequently discovered VMs may be leveraged for follow-on activities such as Service Stop or Data Encrypted for Impact.[1]
| ID | Name | Description |
|---|---|---|
| S1096 | Cheerscrypt |
Cheerscrypt has leveraged |
| S1242 | Qilin | |
| G1048 | UNC3886 |
UNC3886 has used scripts to enumerate ESXi hypervisors and their guest VMs.[5] |
| S1217 | VIRTUALPITA |
VIRTUALPITA can target specific guest virtual machines for script execution.[6] |
This type of attack technique cannot be easily mitigated with preventive controls since it is based on the abuse of system features.
| ID | Name | Analytic ID | Analytic Description |
|---|---|---|---|
| DET0199 | Detection Strategy for Virtual Machine Discovery | AN0572 |
Monitor for execution of hypervisor management commands such as |
| AN0573 |
Detects attempts to enumerate VMs via hypervisor tools like |
||
| AN0574 |
Detects enumeration of VMs using PowerShell ( |
||
| AN0575 |
Detects VM enumeration attempts using virtualization utilities such as VirtualBox ( |