Skip to content
Cloud Security Breaches

Salesloft (Drift) (2025): what the sources say about the cloud incident

Salesloft (Drift) disclosed the incident on 20 Aug 2025. What was exposed, as the sources state it: OAuth tokens for Drift customers' technology integrations, obtained from the Drift AWS environment; Salesloft GitHub repositories downloaded; environment variable secrets exfiltrated. The ledger reads the access path as leaked access keys and secrets with third-party access.

Open the ledger · Report a correction

Disclosed
20 Aug 2025
Incident window
March 22 to September 5, 2025
Cloud or provider
AWS
What was exposed
OAuth tokens for Drift customers' technology integrations, obtained from the Drift AWS environment; Salesloft GitHub repositories downloaded; environment variable secrets exfiltrated
How access was gained
The investigation summary says the threat actor accessed the Salesloft GitHub account (March to June 2025), then accessed Drift's AWS environment and obtained OAuth tokens for customers' integrations, and used them to access data via Drift integrations.
Access path
Leaked access keys and secrets; also Third-party access
Kind of control that addresses it
scope and monitor source-code hosting tokens, keep integration secrets out of repository and build environments, and restrict where integration tokens may be used from

In the words of the source

“The threat actor then accessed Drift’s AWS environment and obtained OAuth tokens for Drift customers’ technology integrations.” (company statement, Salesloft trust site: Drift security update and Mandiant investigation summary)

Primary sources

If a field is wrong or a newer primary source exists, write to the editor with the entry name in the subject.

Sources

  1. Salesloft trust site: Drift security update and Mandiant investigation summary, read 16 Nov 2026

Last reviewed 16 Nov 2026.