Malicious Microsoft Defender Disabled via Registry DisableAntiSpyware (via process_creation)

PremiumReviewedSigma · High · v1
Product
windows
Category
process_creation
Author
HuntRule
Published
2026-10-30
Updated
2026-10-30

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 reg.exe setting the Windows Defender DisableAntiSpyware policy value to one, the defense-evasion action performed by a helper tool in the ELPACO-team Confluence intrusion to turn off protection before ransomware staging. Adversaries disable Defender through this policy key to blind endpoint protection ahead of encryption, so a write enabling DisableAntiSpyware is a strong pre-impact evasion indicator.

Related detections9 linkedT1685 — drag to rearrange
Suspicious Termination of Defender Tray Process via Taskkill
Malicious Windows Defender Disablement via MpCmdRun RemoveDefinitions
Malicious Unsigned VIB Installation on ESXi Host via esxcli (via process_creation)
Suspicious In-Memory PowerShell Execution from Web Server via Automation Assembly (via image_load)
Malicious EDR Evasion Driver Load from AnyDesk Directory via k.sys (via image_load)
Malicious Zemana Vulnerable Driver Load for EDR Termination (via image_load)
Suspicious EDRKillShifter Vulnerable Driver Load from User Temp Directory (via image_load)
Malicious AuKill EDR Killer Kernel Driver Load via Process Explorer Driver (via image_load)
Malicious FIN7 AvNeutralizer EDR Killer Execution via Masqueraded Binary (via process_creation)
Malicious Microsoft Defender Disabled via Registry DisableAntiSpyware (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.