Successful Windows Account Logon via WMI (4624 with WmiPrvSE.exe)

Flags successful 4624 logons tied to WmiPrvSE.exe, indicating WMI-driven authentication on Windows.

FreeReviewedSigma · Low · v2
Product
windows
Service
security
Author
Thomas Patzke (SigmaHQ), DRL 1.1
Published
2019-12-04
Updated
2026-07-31

ATT&CK techniques

Execution
  1. Recon

  2. Resource Dev

  3. Initial Access

  4. Persistence

  5. Priv Esc

  6. Defense Evasion

  7. Cred Access

  8. Discovery

  9. Lateral Movement

  10. Collection

  11. C2

  12. Exfiltration

  13. Impact

What it detects

This rule identifies successful Windows logon events where the initiating process is WmiPrvSE.exe, indicating authentication tied to WMI activity. Attackers may use WMI to execute commands or interact with systems while leveraging existing authentication paths. The detection relies on Windows Security auditing (Event ID 4624) and correlates the logon to the specific process name suffix for WmiPrvSE.exe.

Related detections9 linkedT1047 — drag to rearrange
Malicious WMIexec Style Command Output Redirection to Local Admin Share
Suspicious Impacket Style Command Execution with ADMIN Share Output Redirect
Malicious Shadow Copy Deletion via WMIC via Process Creation (via process_creation)
Suspicious System Reconnaissance Output Redirected to PDF File (via process_creation)
Suspicious Phantom Taurus mssq.bat SQL Execution via WMI (via process_creation)
Malicious Antivirus Removal via WMIC Product Uninstall
Suspicious Remote Process Creation via WMIC by Mallox
Malicious Akira Shadow Copy Deletion via PowerShell WMI (via process_creation)
Suspicious Sysinternals EULA Acceptance Registry Write Linked to INC Ransomware
Successful Windows Account Logon via WMI (4624 with WmiPrvSE.exe)
Pivot detection · T1047 · 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.