Malicious Windows Defender Disable via Policy Registry Keys

PremiumReviewedSigma · Medium · v1
Product
windows
Category
registry_set
Author
HuntRule
Published
2026-05-12
Updated
2026-08-28

ATT&CK techniques

  1. Recon

  2. Resource Dev

  3. Initial Access

  4. Execution

  5. Persistence

  6. Priv Esc

  7. Defense Evasion

  8. Cred Access

  9. Discovery

  10. Lateral Movement

  11. Collection

  12. C2

  13. Exfiltration

  14. Impact

What it detects

This rule detects modification of the Windows Defender policy registry values that switch off antispyware antivirus and real time monitoring as performed in the SystemBC intrusion described by WithSecure. Disabling Defender through policy keys is a defense evasion step attackers take to clear the path for credential theft and ransomware staging.

Related detections9 linkedT1685 — drag to rearrange
Malicious Microsoft Defender Real-Time Monitoring Disabled via Set-MpPreference (via process_creation)
Suspicious Windows Defender Exclusion Added via PowerShell via Process Creation (via process_creation)
Malicious TCC AppleEvents Reset via Tccutil
Suspicious ESXi Management Agent Stop via vpxa init Script (via process_creation)
Malicious ESXi Firewall Disable via esxcli (via process_creation)
Malicious ESXi Syslog Redirection to tmp via esxcli
Suspicious Windows Defender Exclusion Enumeration via reg query (via process_creation)
Malicious Windows Defender Exclusion Added via PowerShell (via process_creation)
Malicious BYOVD EDR Kill via Renamed GMER Driver by Agonizing Serpens
Malicious Windows Defender Disable via Policy Registry Keys
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.