Windows process access indicating potential shellcode injection to lsass.exe

Alerts on high-privilege process access from wmiprvse.exe to lsass.exe consistent with potential shellcode injection behavior.

FreeReviewedSigma · Medium · v5
Product
windows
Category
process_access
Author
Bhabesh Raj (SigmaHQ), DRL 1.1
Published
2022-03-11
Updated
2026-07-31

ATT&CK techniques

Priv Esc → Defense Evasion
  1. Recon

  2. Resource Dev

  3. Initial Access

  4. Execution

  5. Persistence

  6. Defense Evasion

  7. Cred Access

  8. Discovery

  9. Lateral Movement

  10. Collection

  11. C2

  12. Exfiltration

  13. Impact

What it detects

This rule flags Windows process access events with specific GrantedAccess values and an associated call trace containing the string "UNKNOWN". The match is constrained to suspicious source/target process pairs involving Wmiprvse.exe accessing lsass.exe, while excluding several known benign Dell and Visual Studio program-to-program patterns. It matters because abnormal access to sensitive processes like lsass.exe can be used to support covert code execution, and the detection relies on process access telemetry that records GrantedAccess, SourceImage, TargetImage, and call trace context.

Related detections9 linkedT1055 — drag to rearrange
Suspicious Office Application Spawning Script Or Shell Interpreter
Suspicious Network Connection From wabmig.exe (Turian Injection)
Suspicious Outbound Network Connection from Explorer Process
Suspicious AppLaunch.exe Spawned As Injection Target (via process_creation)
Suspicious BugSleep Marker File in Public Directory
Suspicious CRAT Injection Named Pipe ChromeUpdatePipe (via pipe_created)
AsyncRAT Injector libPK.dll Written to Public Folder (via file_event)
FlawedGrace spawning threat injection target
In-Memory Ramnit Process Injection Target Spawned by WmiPrvSE in drIBAN Fraud Operation (via process_creation)
Windows process access indicating potential shellcode injection to lsass.exe
Pivot detection · T1055 · 9 related

Changelog

v5
  1. v5
    Candidate ingested via manual entry.2026-07-31
  2. v4
    Candidate ingested via manual entry.2026-07-31
  3. v3
    Candidate ingested via manual entry.2026-07-31
  4. v2
    Candidate ingested via manual entry.2026-07-31
  5. 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.