Suspicious Windows Defender Exclusion Added via Add-MpPreference

PremiumReviewedSigma · Medium · v1
Product
windows
Category
ps_script
Author
HuntRule
Published
2026-10-01
Updated
2026-10-01

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 use of Add-MpPreference to add Windows Defender path or extension exclusions, a defense-evasion step observed in the intrusion where the actor carved out exclusions before staging malware. Excluding a directory or file type from scanning lets subsequent payloads run undetected. While admins occasionally set exclusions, unexpected additions on endpoints frequently precede malware deployment.

Related detections9 linkedT1685 — drag to rearrange
Malicious Windows Defender Disabled via DefenderControl Utility (via process_creation)
In-Memory Phantom Stealer AMSI and ETW Bypass via In-Memory Function Patching (via ps_script)
INC Ransomware Vulnerable Driver Drop for EDR Termination (via file_event)
SparkRAT Defender Exclusions for ctfmon and C Drivers (via registry_set)
Disable Windows Defender via Service
Uninstall Windows Feature - Defender
Malicious Microsoft Defender Real Time Protection Failure - Native (via windefend)
Malicious Defender for Endpoint eBPF Sensor Deactivation (via linux)
Suspicious Microsoft Defender Exclusion Added via PowerShell Add-MpPreference (via process_creation)
Suspicious Windows Defender Exclusion Added via Add-MpPreference
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.