Windows suspicious access to LSASS.exe with dbgcore.dll/dbghelp.dll call trace from uncommon paths

Alerts on suspicious LSASS access from unusual locations when dbgcore.dll or dbghelp.dll appears 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

Cred Access
  1. Recon

  2. Resource Dev

  3. Initial Access

  4. Execution

  5. Persistence

  6. Priv Esc

  7. Defense Evasion

  8. Discovery

  9. Lateral Movement

  10. Collection

  11. C2

  12. Exfiltration

  13. Impact

What it detects

This rule flags process access to LSASS.exe when the call trace contains dbgcore.dll or dbghelp.dll and the requesting process originates from uncommon filesystem locations. Attackers can use these debugging helper DLLs to perform LSASS memory access and dumping via Windows dump-related APIs. The detection relies on process access telemetry that includes the target image, source image path, and call trace contents to identify potentially malicious access patterns.

Related detections9 linkedT1003.001 — drag to rearrange
Malicious Credential Extraction via Volatility Memory Analysis (via process_creation)
Suspicious Physical Memory Acquisition via WinPmem (via process_creation)
Malicious LSASS Credential Dump via Rundll32 Comsvcs MiniDump via Process Creation (via process_creation)
Suspicious LSASS Credential Access via PowerShell (via process_creation)
Suspicious LSASS Memory Dump via Task Manager After Ivanti Exploitation
Suspicious ProcDump LSASS Memory Dump via process_creation
Malicious Mimikatz Credential Dump Log File Creation (via file_event)
Malicious WDigest UseLogonCredential Enabled for Cleartext Credential Theft (via registry_set)
Suspicious LSASS Memory Dump via Procdump Process Creation
Windows suspicious access to LSASS.exe with dbgcore.dll/dbghelp.dll call trace from uncommon paths
Pivot detection · T1003.001 · 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.