Python-Based Tool LSASS Process Access for Credential Dumping (Windows)

Alerts on process-access attempts to lsass.exe with a Python-related call trace and high granted access.

FreeReviewedSigma · High · v2
Product
windows
Category
process_access
Author
Bhabesh Raj, Jonhnathan Ribeiro (SigmaHQ), DRL 1.1
Published
2023-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 identifies Windows process-access events where a process ending in lsass.exe is targeted with a high privilege access mask, along with a call trace indicative of Python-related modules. The combination of lsass.exe targeting and Python runtime artifacts suggests an attempted credential dumping workflow using a Python-based tool. It relies on process-access telemetry and call stack/call trace information that includes module paths and granted access details.

Related detections9 linkedT1003.001 — drag to rearrange
Malicious WDigest Credential Caching Enabled via Registry (via registry_set)
Malicious Credential Dumping via Mimikatz Sekurlsa Command
Malicious Mimikatz Sekurlsa Logonpasswords Credential Dump
Malicious LSASS Credential Dump via ProcDump (via process_creation)
Malicious LSASS Memory Dump via comsvcs.dll by Salt Typhoon
Malicious LSASS Dump via Process Access (via process_access)
Malicious LSASS Credential Dump with LSASSY - Process (via process_creation)
Malicious LSASS Credential Dump with LSASSY - Admin Share (via security)
Malicious Task Manager Used for LSASS Dump - Kernel (via security)
Python-Based Tool LSASS Process Access for Credential Dumping (Windows)
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.