Response playbooks, investigation guides, and Atomic Red Team tests are Pro-only. Upgrade to unlock the full detection package for THREAT-CloudCLI-ScheduledExfil.

Upgrade to Pro
THREAT-CloudCLI-ScheduledExfil CrowdStrike LogScale · LogScale

Detect Scheduled Transfer via Cloud Sync/Backup CLI Tools in CrowdStrike LogScale

Adversaries increasingly implement Scheduled Transfer (T1029) not with custom malware beacon loops but by abusing legitimate, already-installed cloud sync and backup command-line tools — rclone, restic, aws-cli (s3 sync/cp), azcopy, and gsutil — invoked on a fixed interval via cron, systemd timers, or Windows Task Scheduler. This approach blends with routine backup/sync traffic, uses signed and expected binaries, and often targets attacker-controlled cloud storage (a non-corporate S3 bucket, a personal rclone remote, a throwaway Backblaze/Azure account) rather than a custom C2 server, evading network-signature and IP-reputation detections. This pattern has been widely observed in ransomware pre-encryption exfiltration (rclone is the single most frequently recovered exfiltration tool across ransomware IR engagements) and in insider-driven bulk data theft where a scheduled job is created to stage and ship data outside normal working hours. This detection complements the existing T1029 coverage (which focuses on raw network beaconing and generic scheduled-task-spawns-transfer-tool patterns) by specifically fingerprinting cloud-storage CLI syntax, non-corporate destination indicators, and the scheduler-persistence mechanism used to make the transfer recurring.

MITRE ATT&CK

Tactic
Exfiltration

LogScale Detection Query

CrowdStrike LogScale (LogScale)
cql
// Alert 1: Cloud CLI tool launched by a scheduler parent process
#event_simpleName=ProcessRollup2
| in(field="FileName", values=["rclone.exe", "restic.exe", "aws.exe", "azcopy.exe", "gsutil.exe", "mc.exe"], ignoreCase=true)
| in(field="ParentBaseFileName", values=["taskeng.exe", "taskhostw.exe", "svchost.exe", "schtasks.exe"], ignoreCase=true)
| CommandLine=/(?i)(sync|copy|\bcp\b|\bput\b|push|backup)/
| table([ComputerName, UserName, FileName, CommandLine, ParentBaseFileName, ParentCommandLine, timestamp])
| sort(timestamp, order=desc)

// Alert 2: run as a separate scheduled search — same tool invoked 3+ times with upload verbs, grouped by host/user over 7 days
#event_simpleName=ProcessRollup2
| in(field="FileName", values=["rclone.exe", "restic.exe", "aws.exe", "azcopy.exe", "gsutil.exe"], ignoreCase=true)
| CommandLine=/(?i)(sync|copy|\bcp\b|\bput\b|push)/
| stats count(as=RunCount), earliest(timestamp, as=FirstRun), latest(timestamp, as=LastRun) by ComputerName, UserName, FileName
| RunCount>=3
high severity medium confidence

Two CrowdStrike CQL queries against ProcessRollup2 events. The first matches cloud CLI transfer tools launched with a Task Scheduler or service-host parent and an upload-style verb. The second aggregates the same tool family by host/user over a 7-day window to surface 3 or more upload-verb invocations, capturing the recurring-schedule behavioural signature that complements the single-event detection.

Data Sources

CrowdStrike Falcon ProcessRollup2 eventsFalcon Data Replicator (FDR) process telemetry

Required Tables

ProcessRollup2

False Positives & Tuning

  • Approved backup automation using rclone/restic scheduled via Task Scheduler to a corporate storage destination
  • CI/CD pipelines invoking aws s3 sync or azcopy on a recurring schedule to an approved bucket
  • MSP-managed backup tooling built on rclone for scheduled multi-tenant backup rotation

Other platforms for THREAT-CloudCLI-ScheduledExfil


Testing Methodology

Validate this detection against 3 adversary techniques from Atomic Red Team. Each test below lists the behaviour to exercise and the telemetry you should expect to see. Executable commands and cleanup steps are available with Pro.

  1. Test 1Windows — Scheduled Task Running rclone Sync to External Remote

    Expected signal: Windows Security Event ID 4698 (scheduled task created) for task name 'CloudBackupSync'. Sysmon Event ID 1 for schtasks.exe process creation with '/create /sc MINUTE /mo 30' in the command line. When the task fires: Sysmon Event ID 1 for taskhostw.exe spawning cmd.exe spawning rclone.exe with 'sync' in the command line.

  2. Test 2Windows — Recurring aws s3 sync Invocations Simulating a Scheduled Exfiltration Job

    Expected signal: Sysmon Event ID 1: three Process Create events for aws.exe with 's3', 'sync', and '--endpoint-url' in the command line, spaced a few seconds apart (compressed for testing; production pattern spans days). Sysmon Event ID 3: connection attempts to 127.0.0.1:9999.

  3. Test 3Linux — Systemd Timer Triggering Scheduled restic Backup to External Repository

    Expected signal: Auditd or Sysmon-for-Linux: file write events for /etc/systemd/system/restic-sync-test.service and .timer. Process execution events for systemctl with 'daemon-reload' and 'enable --now'. When the timer fires: execve event for restic with 'backup' argument, PPID belonging to systemd.

Unlock playbooks & atomic tests with Pro

Get the full detection package for THREAT-CloudCLI-ScheduledExfil — response playbook and atomic red team tests, plus investigation guidance and hunting queries.

df00tech Pro — £29/user/month

Response PlaybookInvestigation GuideHunting QueriesAtomic Red Team TestsTuning Guidance

Related Detections