Between August 8 and 18, 2025, an attacker tracked as UNC6395 used stolen OAuth tokens belonging to the Salesloft Drift chatbot integration to export Salesforce data from hundreds of organisations. Affected names include Cloudflare, Google, Zscaler and Palo Alto Networks. The attacker then searched the stolen records for AWS keys, passwords and Snowflake tokens.

What is going on

OAuth is the mechanism that lets one app use another on your behalf without knowing your password. When you connect a chat widget to your CRM, the CRM hands the chat tool a long-lived token. That token is a key that keeps working until someone revokes it.

Think of it as giving a cleaning company a key to your office. Nothing is wrong with the lock, but if the key is copied, the thief walks in through the front door. That is what happened here: the tokens were stolen, and Salesforce saw normal-looking app traffic.

The data itself was the prize twice over. First as customer records, and second as a hiding place for secrets that staff paste into support tickets and notes.

Who is affected

Any organisation that connected the Drift chat widget to Salesforce is in scope. The same risk pattern applies to any other chatbot, form tool or marketing app you have linked to your CRM.

Small businesses are not excluded. The victims named so far are large, but token theft affects whoever installed the integration, not only big brands.

What to do now

  1. Revoke and re-issue every token for the Drift integration and any other chatbot connected to your CRM.
  2. Search your CRM records and support tickets for secrets. Look for strings such as AKIA (the start of an AWS access key) and the word password.
  3. Rotate anything you find. Treat an exposed key as already used, not as a near miss.
  4. Restrict connected-app scopes so each integration can read only the fields it truly needs.
  5. Limit access by IP range where your CRM supports it, so a stolen token is useless from an unknown network.

How to check your own site

This incident started in a connected app, not on a website, but the same habit of leaving old integrations and credentials in place shows up on web servers too. The free Website Security Check looks at outdated CMS versions, known-vulnerable plugins, missing security headers, weak TLS and email-authentication gaps. If you want exposed-file and secret checks alongside active OWASP Top 10 testing, you can run a full scan against a site whose ownership you have verified.

Source: Google Cloud Threat Intelligence, August 2025.