Windows WinRAR or RAR Utility Execution from Non-Default Installation Paths

Alerts on WinRAR/RAR process execution when launched from folders outside standard WinRAR installation paths.

FreeReviewedSigma · Medium · v1
Product
windows
Category
process_creation
Author
Florian Roth (Nextron Systems), Tigzy (SigmaHQ), DRL 1.1
Published
2021-11-17
Updated
2026-07-30

ATT&CK techniques

Collection
  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. C2

  12. Exfiltration

  13. Impact

What it detects

This rule flags process creation events where the executable filename ends with WinRAR/RAR (rar.exe or winrar.exe) but the image path is not located under the typical Program Files WinRAR installation directories. Attackers may run compression utilities from unusual directories to package or stage files while blending into normal tool usage. The detection relies on Windows process creation telemetry, matching the executable name and applying path-based exclusions.

Related detections9 linkedT1560.001 — drag to rearrange
Malicious PXA Stealer Archive Extraction via Renamed WinRAR images.png (via process_creation)
Suspicious Data Staging via Rar Archive With Delete Flag (via process_creation)
Suspicious 7za Archiver Executed from Windows Temp
Suspicious PowerShell Compress-Archive of Signal Configuration by Turla (via ps_script)
Suspicious Oracle Data Export via sqluldr Utility by APT41 (via process_creation)
Suspicious Password Protected Archiving with Hardcoded GoSerpent Key via process_creation
Suspicious Multi-Volume RAR Archiving for Collection by EAGERBEE
Suspicious Archive Staging to ProgramData NetWorks Path via RAR (via process_creation)
Suspicious Selective Archiving via 7-Zip Linked to INC Ransomware Exfiltration
Windows WinRAR or RAR Utility Execution from Non-Default Installation Paths
Pivot detection · T1560.001 · 9 related

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