Malicious Windows Defender Service Disable via Registry

PremiumReviewedSigma · High · v1
Product
windows
Category
registry_set
Author
HuntRule
Published
2026-10-01
Updated
2026-10-01

ATT&CK techniques

Persistence → Defense Evasion
  1. Recon

  2. Resource Dev

  3. Initial Access

  4. Execution

  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 the WinDefend service Start value being set to 4 (disabled) in the registry, preventing Microsoft Defender from launching at boot. This defense-evasion step appears in recurring ransomware playbooks that neutralize endpoint protection before encryption. Disabling the AV service removes real-time protection across reboots.

Related detections9 linkedT1685 — drag to rearrange
Suspicious SmartScreen Disable via Registry Modification via registry_set
Malicious Microsoft Defender Disable via Registry by Key Group
Malicious Microsoft Defender Tamper via Registry Modification
Malicious Defender Real-Time Monitoring Disable via Registry
Registry value change disables ETW logging in .NET Framework/.NET via COMPlus
Sysmon Registry: .NET ETW Logging Disabled via ETWEnabled and COMPlus_ETWEnabled Keys
Malicious Windows Defender Disabled via DefenderControl Utility (via process_creation)
Suspicious Remote Desktop Disable via fDenyTSConnections Registry Modification (via registry_set)
In-Memory Phantom Stealer AMSI and ETW Bypass via In-Memory Function Patching (via ps_script)
Malicious Windows Defender Service Disable via Registry
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.