PowerShell Tamper: Set-MpPreference disables Windows Defender scanning and protections

Flags PowerShell attempts to alter Windows Defender preferences using Set-MpPreference with Allow-style disable/default-action parameters.

FreeReviewedSigma · High · v2
Product
windows
Category
ps_classic_provider_start
Author
frack113, Nasreddine Bencherchali (Nextron Systems) (SigmaHQ), DRL 1.1
Published
2021-06-07
Updated
2026-07-31

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 identifies PowerShell activity starting a classic provider that uses Set-MpPreference to set Windows Defender settings to allow or disable multiple security features. Attackers may use these configuration changes to reduce detection and prevention coverage by turning off scanning, monitoring, and related protections or forcing default actions to allow threats. The detection relies on telemetry capturing PowerShell provider start events where the Data field contains Set-MpPreference and specific disabling or allow-related parameter values.

Related detections9 linkedT1685 — drag to rearrange
Malicious Microsoft Defender Tampering via PowerShell Preference Cmdlets
Suspicious Windows Defender Exclusion via Add-MpPreference (via process_creation)
Malicious Windows Defender Service Tampering via PowerShell (via process_creation)
Windows Defender Disabled via DisableAntiSpyware Registry Key
Suspicious Vulnerable Intel Ethernet Driver Load for BYOVD via SCATTERED SPIDER (via driver_load)
Malicious Defender Disable And Executable Exclusion Via Registry
Malicious UAC Disable via EnableLUA Registry Modification (via registry_set)
Malicious AMSI and ETW Patching via PowerShell Script
Malicious PowMix AMSI Bypass via amsiInitFailed
PowerShell Tamper: Set-MpPreference disables Windows Defender scanning and protections
Pivot detection · T1685 · 9 related

Changelog

v2
  1. v2
    Candidate ingested via manual entry.2026-07-31
  2. v1
    No changelog recorded for this version.2026-07-30

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