A chat bubble on a laptop linked by a key chain to a filing cabinet being opened by an intruder's hand

Between 8 and 18 August 2025, an attacker group tracked as UNC6395 used stolen OAuth tokens from the Salesloft Drift AI chat integration to pull data out of many companies' Salesforce accounts. The group searched the stolen data for AWS keys, passwords and Snowflake tokens. Salesloft revoked all Drift tokens on 20 August 2025.

What is going on

Drift is a chat widget that sits on a website and talks to visitors. To log those conversations as leads, it connects to Salesforce using an OAuth token. That is a long-lived digital key an app keeps so it can read and write your data without asking for a password each time.

Think of it as a spare key you gave to a cleaning company. The attacker did not break your lock; they took the spare key from the cleaner. With it they could query Salesforce as if they were the chat tool.

The goal was not the sales records themselves. It was the secrets people paste into those records: cloud keys, passwords and access tokens left in support tickets and notes.

Diagram of stolen OAuth tokens being used to query Salesforce and where scope limits stop the attack
The attacker never touched the website; a stolen token from the chat integration unlocked Salesforce directly.

Who is affected

Any business that connected the Drift chat widget to Salesforce is in scope. Drift connections to Google Workspace carry the same risk, because the same kind of token was involved.

Your own website software was not attacked here. The weak point was the link between a third-party chat tool and your business systems, so small sites with a chat bubble and a CRM are just as exposed as large ones.

What to do now

  1. Treat every token linked to Drift as compromised. Assume it was used, even though Salesloft revoked tokens on 20 August.
  2. Rotate credentials stored in CRM records. Change any AWS keys, passwords, API keys or Snowflake tokens that appear in Salesforce cases, notes or attachments.
  3. Review your connected apps. In Salesforce and Google Workspace, remove integrations you no longer use and check what access the remaining ones hold.
  4. Tighten the scopes and IP ranges of the connected apps you keep, so a stolen token can read less and only from expected addresses.
  5. Stop pasting secrets into tickets. Keep keys and passwords in a password manager or secrets store, not in free-text CRM fields.

How to check your own site

This breach started outside your website, but it is a good moment to look at what your site exposes. The free Website Security Check flags outdated CMS versions, known-vulnerable plugins, missing security headers, weak TLS and email-authentication gaps. If you want deeper coverage of exposed files and leaked secrets on your own site, you can run a full scan once you have verified ownership.

Source: Google Cloud Threat Intelligence, August 2025.