Suspicious Windows Defender Exclusion Added via PowerShell Add-MpPreference

PremiumReviewedSigma · Medium · v1
Category
process_creation
Author
HuntRule
Published
2026-09-29
Updated
2026-09-29

ATT&CK techniques

Execution
  1. Recon

  2. Resource Dev

  3. Initial Access

  4. Persistence

  5. Priv Esc

  6. Defense Evasion

  7. Cred Access

  8. Discovery

  9. Lateral Movement

  10. Collection

  11. C2

  12. Exfiltration

  13. Impact

What it detects

This rule detects PowerShell using Add-MpPreference to register a Windows Defender exclusion, observed during post-exploitation of CrushFTP servers by Huntress. Attackers add path or process exclusions to prevent detection of tooling staged under directories such as Windows Temp. Disabling protection coverage before dropping payloads is a common defense-evasion precursor, so unexpected exclusion changes warrant review.

Related detections9 linkedT1059.001 — drag to rearrange
Suspicious In-Memory PowerShell Execution from Web Server via Automation Assembly (via image_load)
Suspicious PowerShell AMSI or ETW Tampering
Custom Cobalt Strike Command Execution
Malicious Windows Defender Real-Time Monitoring Disabled via PowerShell
Malicious AMSI Bypass via AmsiUtils amsiInitFailed Manipulation
Malicious Windows Defender Disabled via DefenderControl Utility (via process_creation)
Malicious Fickle Stealer Remote PowerShell Execution From UNC Share (via process_creation)
Suspicious PDF Editor Updater Binary Spawning PowerShell (via process_creation)
PowerShell ExecutionPolicy Set to Bypass via Registry (via registry_set)
Suspicious Windows Defender Exclusion Added via PowerShell Add-MpPreference
Pivot detection · T1059.001 · 9 related

Detection content is published as a reviewed draft. Tune thresholds and exclusions against your own telemetry before enabling this rule for alerting.