Linux: Shell spawned by rsync without -e flag in command line

Flags rsync/rsyncd spawning a shell when rsync lacks the expected " -e " command-line flag.

FreeReviewedSigma · High · v2
Product
linux
Category
process_creation
Author
Florian Roth (SigmaHQ), DRL 1.1
Published
2025-01-18
Updated
2026-07-31

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 identifies process creation where a shell executable (e.g., sh, bash, dash) is launched as a child of rsync (rsync/rsyncd) while the rsync command line does not contain the expected ' -e ' flag. Spawning a shell from a file transfer utility is a strong indicator of misuse, such as remote command execution or exploitation attempts leading to unauthorized actions. It relies on Linux process creation telemetry, specifically parent/child process image paths and command-line content.

Related detections9 linkedT1059 — drag to rearrange
Windows: Suspicious Script/Command Child Processes Spawned by ArcSOC.exe
Suspicious Child Processes Spawned by Browsers on macOS
Suspicious Python Execution via Renamed Synaptics Binary
MSBuild Executing Non-Project File or Remote Payload
Possible Ivanti Pulse Connect Secure Command Injection via License Keys-Status Endpoint (via webserver)
Possible Craft CMS RCE via Query-String CLI Option Injection
Possible Aspera Faspex Pre-Auth RCE via YAML Deserialization in package_relay (via webserver)
Possible Sitecore Pre-Auth RCE via Report.ashx Insecure Deserialization (via webserver)
Possible WatchGuard Pre-Auth RCE via agent login XML-RPC CVE-2022-26318
Linux: Shell spawned by rsync without -e flag in command line
Pivot detection · T1059 · 9 related

Changelog

v2
  1. v2
    Candidate ingested via manual entry.2026-07-31
  2. v1
    No changelog recorded for this version.2026-07-30

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