Malicious Kernel Driver Load from User AppData Directory

PremiumReviewedSigma · High · v1
Product
windows
Category
driver_load
Author
HuntRule
Published
2026-10-15
Updated
2026-10-15

ATT&CK techniques

Persistence → Defense Evasion
  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 detects loading of known malicious kernel driver file names from a user AppData directory which is an abnormal location for signed drivers. NCC Group attributed netfilter and related drivers to a rootkit that manipulates network traffic and hides malicious activity. Loading a driver from a writable user path indicates rootkit installation and kernel level defense evasion.

Related detections9 linkedT1543.003 — drag to rearrange
Malicious Kernel Driver Service Registration for ProjectConfiguration Rootkit
Malicious ValleyRAT KernelQuick Rootkit Service and Shellcode Store Registry Keys
Suspicious Lancefly TdiProxy Driver Loaded
Suspicious Windows Service Masquerading as Windows Defend by APT41 (via registry_set)
Suspicious Service Creation Loading TSVIPSrv.DLL via DreamLoaders (via service_creation)
Malicious HelloNet AppMgmt ServiceDll Persistence via Registry (via registry_set)
Suspicious Service Masquerading as Thumbcache Loader via registry_set
Suspicious Service Masquerading as Google Update in ProgramData via registry_set
Malicious ServiceDll Hijack Of FontCacheSvc via Registry Set
Malicious Kernel Driver Load from User AppData Directory
Pivot detection · T1543.003 · 9 related

Detection content is published as a reviewed draft. Tune thresholds and exclusions against your own telemetry before enabling this rule for alerting.