Windows process contacting Dropbox API from non-Dropbox executables

Alerts when a non-Dropbox executable makes initiated connections to Dropbox API endpoints on Windows.

FreeReviewedSigma · High · v2
Product
windows
Category
network_connection
Author
Florian Roth (Nextron Systems) (SigmaHQ), DRL 1.1
Published
2022-04-20
Updated
2026-07-31

ATT&CK techniques

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

  12. Impact

What it detects

This rule flags outbound network connections where a process initiates communication to Dropbox API endpoints while the connecting executable is not a Dropbox installation path. Attackers may blend command-and-control or exfiltration traffic into legitimate cloud services like Dropbox to avoid detection. The detection relies on Windows network connection telemetry (initiated flag, destination hostnames ending with api.dropboxapi.com or content.dropboxapi.com) and process image path content to exclude likely legitimate Dropbox clients.

Related detections9 linkedT1105 — drag to rearrange
Suspicious Executable Download from Compromised CMS Client Scripts Path (via proxy)
Malicious Silver Fox Stealer Exfiltration Using WhatsAppBackup User Agent
Suspicious HijackLoader PNG Payload Retrieval via ClearFake
Malicious Download Piped to Shell via curl or wget (via process_creation)
Suspicious Data Exfiltration to Azure Blob Storage via AzCopy (via process_creation)
Suspicious File Download via busybox ftpget (via process_creation)
Malicious ActiveMQ CVE-2023-46604 Payload Download via curl or wget
Suspicious PowerShell Download Cradle to Blogspot (via process_creation)
Suspicious Hidden PowerShell WebClient DownloadFile Cradle
Windows process contacting Dropbox API from non-Dropbox executables
Pivot detection · T1105 · 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.