Suspicious Browser History Wipe via RunDll32 ClearMyTracksByProcess

PremiumReviewedSigma · Medium · v1
Product
windows
Category
process_creation
Author
HuntRule
Published
2026-07-27
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 rundll32 invoking InetCpl ClearMyTracksByProcess to clear browsing and cache artifacts. The Gh0stGambit dropper used this to erase indicators after deploying Gh0st RAT. Programmatic history wiping through this control panel handler is a cleanup step rarely performed by normal user activity.

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 Event Log Clearing via Get-WinEvent ClearLog (Qilin)
Suspicious Windows Event Log Clearing via wevtutil on EC2 Host
Suspicious Windows Event Log Clearing via Dire Wolf Ransomware (via process_creation)
Suspicious Browser History Wipe via RunDll32 ClearMyTracksByProcess
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.