ESXi Bulk VM Termination
Description
The following analytic detects when all virtual machines on an ESXi host are abruptly terminated, which may indicate malicious activity such as a deliberate denial-of-service, ransomware staging, or an attempt to destroy critical workloads.
Query · spl
`esxi_syslog`
Message IN (
"*pkill -9 *",
"*process kill*"
)
| rex field=_raw "\s\[(?<user>[^\]]+)\]:\s(?<shell_command>.+)$"
| rex field=_raw "Z (?<dest>[\w\.]+)\s.*:\s(?<esxicli_Command>esxcli\s.+)"
| eval command=mvappend(esxicli_Command, shell_Command)
| where isnotnull(command)
| search (command="pkill -9 vmx-*")
OR
(
command="*esxcli*"
command="*--format-param*"
command="*vm process list*"
command="*awk*"
command="*esxcli vm process kill*"
)
| stats min(_time) as firstTime
max(_time) as lastTime
values(_time) as timeStamp
values(command) as commands
by dest user
| `security_content_ctime(firstTime)`
| `security_content_ctime(lastTime)`
| `esxi_bulk_vm_termination_filter`
Implementation guide
This is based on syslog data generated by VMware ESXi hosts. To implement this search, you must configure your ESXi systems to forward syslog output to your Splunk deployment. These logs must be ingested with the appropriate Splunk Technology Add-on for VMware ESXi Logs, which provides field extractions and CIM compatibility.
Known false positives
- No false positives have been identified at this time.
Analyst notes
Known false positives: No false positives have been identified at this time.