Windows PUA System Informer Driver Load via SystemInformer.sys

Alerts on loading SystemInformer.sys as a Windows driver when matched against known System Informer SHA256 hashes.

FreeReviewedSigma · Medium · v2
Product
windows
Category
driver_load
Author
Florian Roth (Nextron Systems) (SigmaHQ), DRL 1.1
Published
2023-05-08
Updated
2026-07-31

ATT&CK techniques

Persistence → Priv Esc
  1. Recon

  2. Resource Dev

  3. Initial Access

  4. Execution

  5. Defense Evasion

  6. Cred Access

  7. Discovery

  8. Lateral Movement

  9. Collection

  10. C2

  11. Exfiltration

  12. Impact

What it detects

This rule flags Windows kernel driver loads where the loaded image ends with \SystemInformer.sys and the event includes one of the specified SHA256 hashes. Loading a signed or legitimate-looking driver can be abused for persistence or privilege escalation by gaining kernel-level execution. It relies on driver load telemetry that provides the loaded image path and the file hash values.

Related detections9 linkedT1543 — drag to rearrange
Suspicious GitHub Actions Runner In Hidden Directory via Shell (via process_creation)
Suspicious Self-Hosted GitHub Actions Runner Started As Root via Shell (via process_creation)
Suspicious GitHub Self-Hosted Runner Registration via Audit Log (via github)
Malicious Fire Ant Hypervisor Backdoor Artifacts on ESXi and vCenter (via file_event)
Suspicious D-Bus System Service Persistence File Creation
Malicious BRICKSTORM Backdoor Execution via Masqueraded Binary Path
Suspicious SonicWall SMA init.d Persistence Launching deploy_new.py
Malicious Linux XorDDoS gcc.pid Device Marker File via file_event
Windows Code Integrity: Blocked Driver Load Due to Revoked Certificate (Event ID 3023)
Windows PUA System Informer Driver Load via SystemInformer.sys
Pivot detection · T1543 · 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.