Operator On The Wire
Join
← Back to Knowledge Base
BLUE TEAM / THREAT HUNT / WINDOWS / EXFILTRATION

Cloud Sync Abuse

This note documents detection patterns related to Cloud Sync Abuse within Windows environments.


Direct Indicators

LogEvent IDMeaningForensic ValueNotes
Security4688Process creationCriticalDetects sync client execution and abuse tooling.
Sysmon1Process creationCriticalBest lineage source for sync abuse chains.
Sysmon11File createCriticalSensitive files copied into sync folders.
Sysmon3Network connectionCriticalSync client outbound transfer.
Sysmon22DNS queryHighCloud provider resolution.
Security4663File accessHighSensitive file read before sync.

Indirect Indicators

IndicatorWhat To Look ForForensic ValueNotes
Sensitive files copied into OneDrive/DropboxCredential stores / archivesCriticalCore exfil clue.
Sync client launched by shell/scriptNon-user patternCriticalStrong anomaly.
Burst file creation in sync pathMass stagingCriticalExfil pattern.
Sync immediately after archive creationArchive → cloud chainCriticalHigh-confidence exfil sequence.
Unusual provider on enterprise hostRare sync softwareHighValuable anomaly.
DNS + outbound spikeCloud transfer timingHighConfirms movement.

Common Tools

ToolUsage
OneDriveNative cloud sync
DropboxExternal sync
Google DriveFile exfil
rcloneScripted cloud exfil

Relevant Artifacts

  • Security Event IDs 4688, 4663
  • Sysmon Event IDs 1, 11, 3, 22
  • Sync folders:
    • OneDrive
    • Dropbox
    • Google Drive
  • Archive files
  • DNS logs
  • Prefetch for sync client

MITRE ATT&CK References

  • T1567 Exfiltration to Cloud Storage

Decision Tree

  1. Which sync platform?

    • OneDrive
    • Dropbox
    • Drive
    • rclone
  2. Which files staged?

    • Documents
    • Archives
    • Credentials
  3. User-driven or scripted?

    • explorer
    • cmd
    • powershell
  4. Outbound transfer observed?

    • DNS
    • Network burst
  5. Expand:

    • Archive source
    • Credential theft
    • User scope
  6. Scope:

    • Single file
    • Bulk exfil
    • Campaign pattern

Example Detection Templates

KQL

Sysmon
| where EventID == 11
| where TargetFilename has_any ("OneDrive","Dropbox","Google Drive")
| project TimeGenerated, Computer, TargetFilename
Sysmon
| where EventID == 3
| where Image has_any ("OneDrive.exe","Dropbox.exe","rclone.exe")
| project TimeGenerated, Computer, Image, DestinationIp

EQL

file where file.path like "*OneDrive*" or file.path like "*Dropbox*"
sequence by host.name with maxspan=10m
  [ file where file.path like "*OneDrive*" ]
  [ network where process.name in ("OneDrive.exe","Dropbox.exe","rclone.exe") ]

Sigma

title: Cloud Sync Abuse Detection
id: 9a4c2f11-cloud-sync-abuse
status: experimental
description: Detects suspicious file staging into cloud sync folders
references:
  - https://attack.mitre.org/
author: Vergil
date: 2026-03-07
logsource:
  product: windows
  service: sysmon
detection:
  selection:
    EventID: 11
  keywords:
    TargetFilename|contains:
      - 'OneDrive'
      - 'Dropbox'
      - 'Google Drive'
  condition: selection and keywords
fields:
  - TargetFilename
falsepositives:
  - Legitimate sync activity
level: high
tags:
  - attack.exfiltration

Mitigation & Hardening

Control AreaMitigationEffectivenessNotes
Watch sync foldersDetect sensitive stagingCriticalStrong signal
Correlate archive + syncHigh-confidence exfilCriticalPowerful triage
Monitor sync clientsRare scripted launchesHighValuable anomaly
DNS visibilityCloud provider timingHighStrong enrichment
Restrict unsanctioned sync toolsReduce abuseHighPrevent exfil