Windows Driver Load from Temporary Directory Paths

Detects Windows driver loads whose ImageLoaded path contains the temporary directory (\Temp\).

FreeReviewedSigma · High · v2
Product
windows
Category
driver_load
Author
Florian Roth (Nextron Systems) (SigmaHQ), DRL 1.1
Published
2017-02-12
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 driver loads where the loaded image path contains the temporary directory segment '\Temp\'. Loading a driver from a temp location is suspicious because it may indicate an attempt to stage or execute privileged code from a transient location. The detection relies on telemetry that records the driver image path for driver load events.

Related detections9 linkedT1543.003 — drag to rearrange
Malicious Service Created With Binary Path in ProgramData
Malicious Abyss Locker wmihelper SSH Backdoor Deployment (via file_event)
Malicious AuKill EDR Killer Kernel Driver Load via Process Explorer Driver (via image_load)
Suspicious TermService ServiceDll Hijack via Registry (via registry_set)
Suspicious Service Creation Named RDP-Controller via sc.exe (via process_creation)
Suspicious Service or Task Named windowsinspectionupdate (via process_creation)
Malicious Service Persistence via sc.exe Creating msdnetsvc
Suspicious Stately Taurus Masqueraded Service and Task Persistence via process_creation
Malicious Vulnerable Driver Load for EDR Evasion (via image_load)
Windows Driver Load from Temporary Directory Paths
Pivot detection · T1543.003 · 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.