Windows: Filter Driver Unload via fltMC.exe

Flags fltMC.exe executions that include "unload" to indicate potential filter driver unloading for defense impairment.

FreeReviewedSigma · Medium · v2
Product
windows
Category
process_creation
Author
Nasreddine Bencherchali (Nextron Systems) (SigmaHQ), DRL 1.1
Published
2023-02-13
Updated
2026-07-31

ATT&CK techniques

Defense Evasion
  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 process executions where fltMC.exe is used with an unload command, indicating an attempt to unload a filter driver. Attackers may use this to impair endpoint monitoring or disrupt security components tied to filesystem filtering. It relies on Windows process creation telemetry, matching the process image/original filename and command-line text for "unload". Optional exclusions reduce noise from specific installer or agent-related unload activity.

Related detections9 linkedT1070 — drag to rearrange
Suspicious Browser History Wipe via Rundll32 ClearMyTracksByProcess (via process_creation)
USN Change Journal Deletion via Fsutil (via process_creation)
Suspicious Salesforce Query History Deletion Anti-Forensics
Suspicious Browser History Clearing via RunDll32 InetCpl ClearMyTracksByProcess (via process_creation)
Suspicious Clearing of hosts.deny Access Restrictions on Linux
Windows Process Creation: Command-Line Deletion of IIS Logs
Kubernetes Audit: Deleted Events
Linux Package Removal via yum, apt, dpkg, or rpm Commands
Windows Tomcat Log File Deletion Indicating Possible Forensic Evidence Destruction
Windows: Filter Driver Unload via fltMC.exe
Pivot detection · T1070 · 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.