Potential Data Exfiltration via Rclone
Description
Identifies abuse of rclone (or a renamed copy, e.g. disguised as a security or backup utility) to exfiltrate data to cloud storage or remote endpoints. Rclone is a legitimate file sync tool; threat actors rename it to blend with administrative traffic and use copy/sync with cloud backends (e.g. :s3:) and include filters to exfiltrate specific file types.
Query · eql
process where host.os.type == "windows" and event.type == "start" and
(process.name : "rclone.exe" or ?process.pe.original_file_name == "rclone.exe") and process.args : ("copy", "sync") and
not process.args : ("--config=?:\\Program Files\\rclone\\config\\rclone\\rclone.conf", "--config=?:\\Program Files (x86)\\rclone\\config\\rclone\\rclone.conf") and
not process.executable : ("?:\\Program Files*", "\\Device\\HarddiskVolume*\\Program Files*")
Implementation guide
This rule is designed for data generated by Elastic Defend, which provides native endpoint detection and response, along with event enrichments designed to work with our detection rules.
Setup instructions: https://ela.st/install-elastic-defend
Additional data sources
This rule also supports the following third-party data sources. For setup instructions, refer to the links below:
Analyst notes
Investigating Potential Data Exfiltration via Rclone
Rclone is a legitimate file synchronization tool. Threat actors abuse it (often renamed, e.g. to TrendFileSecurityCheck.exe) to exfiltrate data to S3, HTTP endpoints, or other cloud backends, using copy/sync with --include filters and high --transfers to move specific file types at scale.
Possible investigation steps
- Confirm the command line for
copy/sync, cloud backend (e.g.:s3:,:http), and options like--include,--transfers,-P. - If the process name is not
rclone.exe, compare withprocess.pe.original_file_name; a mismatch indicates a renamed copy used to evade name-based detection. - From the command line, identify the source path (e.g. UNC or local) and the remote backend (S3 bucket, HTTP endpoint) as the exfil destination.
- Review
--include/--excludeand--max-age/--max-sizeto understand what data was targeted (documents, CAD, archives, etc.). - Correlate with the process executable path (recently dropped?), parent process, and user; look for outbound network to the same backend.
False positive analysis
- Legitimate backup or sync jobs using rclone from a known path and config may trigger; allowlist by process path or
--configpath for approved rclone usage.
Response and remediation
- Terminate the rclone process and isolate the host if exfiltration is confirmed.
- Identify and revoke access to the destination (S3 bucket, API keys, etc.); preserve logs for the exfil session.
- Determine scope of data exposed and notify stakeholders; rotate credentials and secrets that may have been in exfiltrated paths.