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 UAC Disable via EnableLUA Registry Modification (via registry_set)
Malicious AMSI and ETW Patching via PowerShell Script
Malicious PowMix AMSI Bypass via amsiInitFailed
Suspicious ThrottleStop Driver Abuse for Defense Evasion in Ransomware Attacks
Malicious Disabling of Microsoft Defender Real-Time Protection via SystemSettingsAdminFlows by DeadLock Ransomware
Suspicious Security Software Uninstallation via WMIC Product Call Uninstall (Chaos Ransomware)
Suspicious Security Product Uninstall via wmic product call uninstall
Suspicious Windows Defender Exclusion Added for ProgramData (via process_creation)
Windows Firewall Disabled via netsh advfirewall
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.