Windows Process Access: WerFaultSecure accessing MsMpEng with dbgcore.dll/dbghelp.dll call traces

Alerts on WerFaultSecure.exe accessing MsMpEng.exe with dbgcore/dbghelp DLLs in the call trace.

FreeReviewedSigma · High · v2
Product
windows
Category
process_access
Author
Swachchhanda Shrawan Poudel (Nextron Systems) (SigmaHQ), DRL 1.1
Published
2025-11-27
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 process access events on Windows where WerFaultSecure.exe accesses MsMpEng.exe, and the call trace includes dbgcore.dll and dbghelp.dll. Such debugger-related module traces alongside access to MsMpEng may indicate attempts to interfere with endpoint security operations. It relies on Sysmon ProcessAccess telemetry that includes call trace data for the accessing and target processes.

Related detections9 linkedT1685 — drag to rearrange
Malicious Windows Defender Disablement via MpCmdRun RemoveDefinitions
Malicious Unsigned VIB Installation on ESXi Host via esxcli (via process_creation)
Suspicious In-Memory PowerShell Execution from Web Server via Automation Assembly (via image_load)
Malicious EDR Evasion Driver Load from AnyDesk Directory via k.sys (via image_load)
Malicious Zemana Vulnerable Driver Load for EDR Termination (via image_load)
Suspicious EDRKillShifter Vulnerable Driver Load from User Temp Directory (via image_load)
Malicious AuKill EDR Killer Kernel Driver Load via Process Explorer Driver (via image_load)
Malicious FIN7 AvNeutralizer EDR Killer Execution via Masqueraded Binary (via process_creation)
Suspicious Process Explorer Kernel Driver Dropped as PED.sys via File Creation (via file_event)
Windows Process Access: WerFaultSecure accessing MsMpEng with dbgcore.dll/dbghelp.dll call traces
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.