huntrule

Windows driver load of HackSys Extreme Vulnerable Driver (HEVD.sys) via image hash

Flags Windows systems when HEVD driver \HEVD.sys is loaded with known IMPHASH values.

FreeReviewedSigma · High · v2
Product
windows
Category
driver_load
Author
Nasreddine Bencherchali (Nextron Systems) (SigmaHQ), DRL 1.1
Published
2022-08-18
Updated
2026-07-31
AnalysisDetection

ATT&CK techniques

Persistence → Priv Esc

  1. Recon

  2. Resource Dev

  3. Initial Access

  4. Execution

  5. Persistence

  6. Priv Esc

  7. Defense Evasion

  8. Cred Access

  9. Discovery

  10. Lateral Movement

  11. Collection

  12. C2

  13. Exfiltration

  14. Impact

What it detects

This rule flags loading of the intentionally vulnerable Windows kernel driver HEVD.sys by matching the loaded image path and specific IMPhash values. Loading this driver is notable because it provides kernel-level functionality that can be leveraged for privilege escalation and other impacts. The detection relies on Windows driver load telemetry that includes the loaded image name/path and its hash (IMPhASH).

Reporting behind it

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 of HackSys Extreme Vulnerable Driver (HEVD.sys) via image hash
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.