Windows Defender Exclusion Path Added via Add-MpPreference

PremiumReviewedSigma · High · v1
Product
windows
Category
process_creation
Author
HuntRule
Published
2026-09-28
Updated
2026-09-28

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 PowerShell adding a Windows Defender exclusion path with Add-MpPreference, a defense-evasion step that lets subsequent payloads run without antivirus inspection. Huntress observed this during ScreenConnect post-exploitation to shield dropped tooling. Attacker use typically excludes staging directories immediately before payload delivery.

Related detections9 linkedT1685 — drag to rearrange
Malicious ELAM Driver Disable via Bcdedit
Suspicious Windows Defender Exclusion Added via PowerShell Add-MpPreference
Suspicious Security Product Process Termination via Named Utility
Suspicious Windows Defender Disabling via SystemSettingsAdminFlows
Suspicious Hosts File Modification to Block Security Vendors via file_event
Malicious Windows Defender Real-Time Protection Disabled via Registry
Malicious Vulnerable Driver Load via TfSysMon.sys BYOVD (via driver_load)
Suspicious Defendnot Antivirus Disabling Component Dropped in ProgramData (via file_event)
Malicious Removal of Defender Safe Mode Service Registration via Process Creation
Windows Defender Exclusion Path 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.