Malicious Windows Defender Exclusion Added via Command Line

PremiumReviewedSigma · Medium · v1
Product
windows
Category
process_creation
Author
HuntRule
Published
2026-10-07
Updated
2026-10-07

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 the creation of Windows Defender scan exclusions through PowerShell MpPreference cmdlets. DarkGate and related crimeware loaders add exclusion paths for their staging directories so subsequently dropped payloads are not scanned, weakening endpoint defenses before further execution.

Related detections9 linkedT1685 — drag to rearrange
Malicious Defender Real-Time Monitoring Disabled via Process Creation
Suspicious Exchange IIS Worker Loading GhostContainer Module (via image_load)
Suspicious Dell DBUtilDrv2 Vulnerable Driver Load via driver_load
Suspicious Service ACL Hardening via sc.exe sdset (via process_creation)
Malicious Snatch Ransomware SuperBackupMan SafeBoot Service Registration
Malicious Microsoft Defender Tampering via Registry Values
Malicious Windows Defender DisableAntiSpyware Registry Modification
Malicious Windows Defender Tampering via Set-MpPreference (via ps_script)
Suspicious Antivirus Uninstallation via msiexec (via process_creation)
Malicious Windows Defender Exclusion Added via Command Line
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.