Suspicious WMI Query Against Windows Defender Namespace via wmic (via process_creation)

PremiumReviewedSigma · Medium · v1
Product
windows
Category
process_creation
Author
HuntRule
Published
2026-09-16
Updated
2026-09-16

ATT&CK techniques

Execution
  1. Recon

  2. Resource Dev

  3. Initial Access

  4. Persistence

  5. Priv Esc

  6. Defense Evasion

  7. Cred Access

  8. Discovery

  9. Lateral Movement

  10. Collection

  11. C2

  12. Exfiltration

  13. Impact

What it detects

This rule detects wmic querying the Windows Defender WMI namespace, used by Sandworm to inspect and manipulate antivirus exclusions during the KMS campaign. Direct wmic access to the Defender namespace is uncommon in normal operations. It often precedes tampering with protection settings.

Related detections9 linkedT1685 — drag to rearrange
Malicious Microsoft Defender Tampering via PowerShell Preference Cmdlets
Suspicious Windows Defender Exclusion via Add-MpPreference (via process_creation)
Malicious Windows Defender Service Tampering via PowerShell (via process_creation)
Windows Defender Disabled via DisableAntiSpyware Registry Key
Lateral Movement via WMIC Remote Process Creation
Suspicious Vulnerable Intel Ethernet Driver Load for BYOVD via SCATTERED SPIDER (via driver_load)
Malicious Defender Disable And Executable Exclusion Via Registry
Malicious UAC Disable via EnableLUA Registry Modification (via registry_set)
Malicious AMSI and ETW Patching via PowerShell Script
Suspicious WMI Query Against Windows Defender Namespace via wmic (via process_creation)
Pivot detection · T1685 · 9 related

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