Suspicious Kernel Driver Written to AppData Temp Linked to RansomHub EDR Killers

PremiumReviewedSigma · High · v1
Product
windows
Category
file_event
Author
HuntRule
Published
2026-10-02
Updated
2026-10-02

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 a .sys kernel driver file being written into a user AppData Temp directory, a staging behavior used by RansomHub-associated EDR-killer tooling such as EDRKillShifter. Legitimate drivers are almost never dropped to per-user temp paths, so a driver in AppData Temp strongly suggests bring-your-own-vulnerable-driver defense evasion.

Related detections9 linkedT1685 — drag to rearrange
Malicious Vulnerable Driver Load by GentleKiller BYOVD EDR Killer
Suspicious Service binPath Hijack Followed by System Reboot
Malicious Known Vulnerable Driver Load for BYOVD Attack
Malicious Bring-Your-Own-Vulnerable-Driver Load for EDR Killing
Suspicious Qilin EDR Killer BYOVD Service Installation via sc
Suspicious Windows Defender Service Disabled via Registry (via registry_set)
Suspicious Windows Defender or Firewall Service Disabled via Registry
Malicious Windows Defender Service Disable via Registry
Suspicious WMI Event Consumer Creation for MbRemoval Persistence via ps_script
Suspicious Kernel Driver Written to AppData Temp Linked to RansomHub EDR Killers
Pivot detection · T1685 · 9 related

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