Malicious ELAM Driver Disable via Bcdedit

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

ATT&CK techniques

Persistence → Priv Esc
  1. Recon

  2. Resource Dev

  3. Initial Access

  4. Execution

  5. Defense Evasion

  6. Cred Access

  7. Discovery

  8. Lateral Movement

  9. Collection

  10. C2

  11. Exfiltration

  12. Impact

What it detects

This rule detects bcdedit disabling Early Launch Anti-Malware drivers which prevents boot-time protection from loading and allows unsigned or malicious drivers to initialize. This tampering appears in ransomware playbooks that clear the way for kernel-level evasion. Disabling ELAM undermines the boot integrity chain that would otherwise block untrusted drivers.

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)
Malicious ELAM Driver Disable via Bcdedit
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.