Suspicious Child Process Spawned by WinRAR.exe on Windows

Alerts when WinRAR.exe launches command, scripting, or proxy execution binaries on Windows.

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

ATT&CK techniques

Execution
  1. Recon

  2. Resource Dev

  3. Initial Access

  4. Persistence

  5. Priv Esc

  6. Defense Evasion

  7. Cred Access

  8. Discovery

  9. Lateral Movement

  10. Collection

  11. C2

  12. Exfiltration

  13. Impact

What it detects

This rule flags Windows process creation events where WinRAR.exe spawns execution-related child processes matching common LOLBin patterns (e.g., cmd.exe, PowerShell, mshta, regsvr32, rundll32, cscript, wscript). Such behavior matters because WinRAR activity is often abused as an initial execution vector to run arbitrary commands through spawned system interpreters and script execution binaries. It relies on telemetry that records parent/child process relationships, including ParentImage and Image/OriginalFileName fields.

Related detections9 linkedT1203 — drag to rearrange
Malicious Script Execution from WinRAR Extraction Directory via CVE-2023-38831
Suspicious Execution From WinRAR Temporary Extraction Path via Command Line (via process_creation)
Malicious Shell Execution via Foomatic-rip Print Filter through CUPS Exploit
Suspicious Network Connection From CUPS Foomatic-Rip Child Process
Antivirus signatures matching APT malware naming patterns
Antivirus Remote Access Tool Signature Matches Known RAT Names
Malicious Microsoft Word Spawning Anomalous Child Process via CVE-2023-36884 (via process_creation)
Possible ExifTool CVE-2026-3102 Command Injection via Child Process Spawn (via process_creation)
Malicious Equation Editor Child Process Execution via process_creation
Suspicious Child Process Spawned by WinRAR.exe on Windows
Pivot detection · T1203 · 9 related

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