Windows Process Creation: SharpEvtMute Execution (Event Log Tampering)

Alerts on SharpEvtMute.exe runs with event-log filter and encoded command-line parameters on Windows.

FreeReviewedSigma · High · v2
Product
windows
Category
process_creation
Author
Florian Roth (Nextron Systems) (SigmaHQ), DRL 1.1
Published
2022-09-07
Updated
2026-07-31

ATT&CK techniques

  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 execution of SharpEvtMute, a Windows utility associated with tampering with event logs. Attackers may use it to impair visibility by altering or suppressing Windows event records. The detection relies on Windows process creation telemetry, matching the SharpEvtMute executable name, a related description string, and command-line arguments that include specific filter parameters and encoded options.

Related detections9 linkedT1685.001 — drag to rearrange
Malicious Security Event Log Disabled via wevtutil
Malicious SQL Server Auditing Deactivated (via application)
Malicious Event Log Deactivation or Size Reduction - Command (via process_creation)
Malicious Audit Policy Disabled by Command Line (via process_creation)
Suspicious IIS Logging Disabled via appcmd
Malicious SQL Server Database Auditing Deactivated (via application)
Malicious Audit Policy Disabled by Command Line (via security)
Malicious Event Log Tampering via wevtutil Channel Disable by FunkSec Ransomware (via process_creation)
OCSP Responder Auditing Settings Changed or Disabled (via security)
Windows Process Creation: SharpEvtMute Execution (Event Log Tampering)
Pivot detection · T1685.001 · 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.