PowerShell Hyper-V Cmdlets Execution via Script Blocks (New-VM, Set-VMFirmware, Start-VM)

Alerts when PowerShell script blocks use Hyper-V VM creation or start cmdlets (New-VM, Set-VMFirmware, Start-VM).

FreeReviewedSigma · Medium · v2
Product
windows
Category
ps_script
Author
frack113 (SigmaHQ), DRL 1.1
Published
2022-04-09
Updated
2026-07-31

ATT&CK techniques

Defense Evasion
  1. Recon

  2. Resource Dev

  3. Initial Access

  4. Execution

  5. Persistence

  6. Priv Esc

  7. Cred Access

  8. Discovery

  9. Lateral Movement

  10. Collection

  11. C2

  12. Exfiltration

  13. Impact

What it detects

This rule matches PowerShell script block content that includes Hyper-V cmdlets associated with creating a VM, configuring its firmware, and starting it. Such activity can be used to stage or run operations inside a virtual instance to reduce visibility and complicate investigations. It relies on Script Block Logging telemetry that records the executed PowerShell script text.

Related detections5 linkedT1564.006 — drag to rearrange
Suspicious Windows Subsystem for Linux (WSL) Installation - Command (via process_creation)
Suspicious Windows Subsystem for Linux (WSL) Package Turned on - Native (via setup)
Suspicious Windows Subsystem for Linux (WSL) Installation - PowerShell (via powershell)
Suspicious Detection of Default a Windows Host Name in Login Attempts (via security)
Windows VirtualBox Driver Registration or VM Startup via Process Command Line
PowerShell Hyper-V Cmdlets Execution via Script Blocks (New-VM, Set-VMFirmware, Start-VM)
Pivot detection · T1564.006 · 5 related

Changelog

v2
  1. v2
    Candidate ingested via manual entry.2026-07-31
  2. v1
    No changelog recorded for this version.2026-07-30

Detection content is published as a reviewed draft. Tune thresholds and exclusions against your own telemetry before enabling this rule for alerting.