Possible Driver Enumeration via Driverquery for Rootkit Discovery

PremiumReviewedSigma · Low · v1
Product
windows
Category
process_creation
Author
HuntRule
Published
2026-10-16
Updated
2026-10-16

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 detects execution of the driverquery utility used to enumerate installed kernel drivers. NCC Group observed this discovery step around deployment of the malicious netfilter driver. While the tool is legitimate its use in interactive attacker sessions can indicate reconnaissance for driver based persistence.

Related detections9 linkedT1543.003 — drag to rearrange
Malicious Kernel Driver Load from User AppData Directory
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 Kernel Driver Service Registration for ProjectConfiguration Rootkit
Malicious ServiceDll Hijack Of FontCacheSvc via Registry Set
Suspicious Service Installation Masquerading as SQLExplorer by Lazarus
Possible Driver Enumeration via Driverquery for Rootkit Discovery
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.