Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →cyberstrikeus/T1673_virtual-machine-discovery
An adversary may attempt to enumerate running virtual machines (VMs) after gaining access to a host or hypervisor.
Passed 16 of 22 test cases with the skill, and 8 of 22 without it.
and 4 more in the full report
8 fixed8 passed either way6 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 8 test cases the skill fixed. Same model, same prompt, with and without the skill.
What exact finding description is recorded in the risk assessment table when Virtual Machine Discovery is found to be applicable in an environment?
| Checked | Without skill | With skill |
|---|---|---|
| State the finding title as Virtual Machine Discovery technique applicable. | Missed | Passed |
The instructions your model reads when the skill loads.
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). 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.
Platforms: ESXi, Linux, macOS, Windows
Identify Attack Surface: Determine if the target environment is susceptible to Virtual Machine Discovery by examining the target platforms (ESXi, Linux, macOS).
Assess Existing Defenses: Review whether mitigations for T1673 are in place. If defenses are absent or misconfigured, this technique may be exploitable.
Execute Test: Use tools and methods described in the MITRE ATT&CK page and external references below.
Note: No Atomic Red Team tests available for this technique. See Atomic Red Team GitHub for updates.
No specific mitigations documented for this technique.
test cases passed, vs 8 / 22 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.