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 |
This type of attack technique cannot be easily mitigated with preventive controls since it is based on the abuse of system features.
ID | Data Source | Data Component | Detects |
---|---|---|---|
DS0017 | Command | Command Execution |
Monitor command-line arguments that may involve listing virtual machines. On ESXi hosts, monitor for commands such as Analytic 1 - Command Execution (ESXi)
Analytic 1 - Command Execution (Linux/macOS)
Analytic 1 - Command Execution (Windows - Hyper-V or VMWare Workstation)
|