Windows Process Access Indicates Potential Shellcode Injection via LSASS

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

FreeReviewedSigma · Medium · v7
Product
windows
Category
process_access
Author
Bhabesh Raj (SigmaHQ), DRL 1.1
Published
2022-03-11
Updated
2026-09-15

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 where the caller requests specific GrantedAccess values that are consistent with potential shellcode injection behavior, with a CallTrace containing 'UNKNOWN'. It excludes several known benign process relationships, including interactions involving Wbem Wmiprvse.exe to lsass.exe and certain Dell, Visual Studio, Avira, or service shell scenarios. Telemetry relies on process access auditing that includes GrantedAccess, SourceImage, TargetImage, and CallTrace.

Related detections9 linkedT1055 — drag to rearrange
Malicious AddInProcess32 Network Beacon on PureRAT C2 Ports
Suspicious Payload Staging in ProgramData IntelDriver Folder (via file_event)
Possible DarkGate Process Injection via iTunesHelper Spawning vbc.exe
Suspicious PowerShell Shellcode Loader via Function Pointer Delegate
Suspicious Named Pipe Created by Kazuar Backdoor for Interprocess Command Channel
Suspicious SmallTiger Backdoor DLL Load via Image Load
Suspicious svchost Execution With Anomalous Arguments via DeedRAT (via process_creation)
Suspicious Sang Loader Execution with Install or PassUAC Arguments
Suspicious GodRAT Shellcode Injection via Puppet Argument (via process_creation)
Windows Process Access Indicates Potential Shellcode Injection via LSASS
Pivot detection · T1055 · 9 related

Changelog

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