Malicious Defender Disable And Executable Exclusion Via Registry

PremiumReviewedSigma · High · v1
Product
windows
Category
registry_set
Author
HuntRule
Published
2026-09-12
Updated
2026-09-12

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 registry modifications that disable Microsoft Defender or add a broad executable-file exclusion. BlackByte tampered with Defender policy keys to disable protection and exclude all .exe files before deploying its ransomware. Disabling antivirus and whitelisting entire file types via the registry is a defense-evasion step that clears the way for payload execution.

Related detections9 linkedT1685 — drag to rearrange
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)
Suspicious Process Explorer Kernel Driver Dropped as PED.sys via File Creation (via file_event)
Malicious Windows Defender Tampering via Set-MpPreference and Add-MpPreference (via ps_script)
Suspicious PowerShell AMSI Bypass via 8220 Gang Hadooken Loader
Malicious Microsoft Defender Services Stopped via sc.exe
Suspicious Microsoft Defender Definitions Removed via MpCmdRun
Malicious Defender Disable And Executable Exclusion 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.