Suspicious Event Log Clearing via Get-WinEvent ClearLog (Qilin)

PremiumReviewedSigma · High · v1
Product
windows
Category
ps_script
Author
HuntRule
Published
2026-08-08
Updated
2026-08-28

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 detects PowerShell clearing Windows event logs by enumerating logs with Get-WinEvent and invoking ClearLog. The Qilin group wipes logs to destroy forensic evidence around encryption. Programmatic clearing of event logs is a hallmark anti-forensic action.

Related detections9 linkedT1685.005 — drag to rearrange
Suspicious Mass Windows Event Log Clearing via PowerShell (via ps_script)
Malicious Event Log Clear Attempt - Wmi (via process_creation)
Malicious Event Log Clear Attempt - Command (via process_creation)
Malicious Event Log Cleared Using Diagnostics - Via PowerShell (via powershell)
Malicious Clearing of Windows Event Logs (via process_creation)
Suspicious Event Log Clearing via wevtutil During Ransomware Activity
Suspicious Windows Event Log Clearing via wevtutil on EC2 Host
Suspicious Browser History Wipe via RunDll32 ClearMyTracksByProcess
Suspicious Windows Event Log Clearing via Dire Wolf Ransomware (via process_creation)
Suspicious Event Log Clearing via Get-WinEvent ClearLog (Qilin)
Pivot detection · T1685.005 · 9 related

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