Windows Process Creation: Raccine Removal via taskkill, registry and scheduled task deletion

Detects command-line activity that stops and removes Raccine components through process killing, registry deletion, and scheduled task removal.

FreeReviewedSigma · High · v1
Product
windows
Category
process_creation
Author
Florian Roth (Nextron Systems) (SigmaHQ), DRL 1.1
Published
2021-01-21
Updated
2026-07-30

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 Windows command lines consistent with removing Raccine components by stopping processes, deleting registry entries, and removing scheduled tasks. Attackers may impair or disable defensive tools to reduce incident detection or persistence of security controls. It relies on process creation telemetry and matches specific command-line substrings for taskkill, reg delete of the "Raccine Tray" key, and schtasks /DELETE for Raccine Updater.

Related detections9 linkedT1685 — drag to rearrange
Malicious Microsoft Defender Tampering via PowerShell Preference Cmdlets
Suspicious Windows Defender Exclusion via Add-MpPreference (via process_creation)
Malicious Windows Defender Service Tampering via PowerShell (via process_creation)
Windows Defender Disabled via DisableAntiSpyware Registry Key
Suspicious Vulnerable Intel Ethernet Driver Load for BYOVD via SCATTERED SPIDER (via driver_load)
Malicious Defender Disable And Executable Exclusion Via Registry
Malicious UAC Disable via EnableLUA Registry Modification (via registry_set)
Malicious AMSI and ETW Patching via PowerShell Script
Malicious PowMix AMSI Bypass via amsiInitFailed
Windows Process Creation: Raccine Removal via taskkill, registry and scheduled task deletion
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.