Google's threat intelligence team reported that an attacker it tracks as UNC6395 used stolen OAuth tokens from the Salesloft Drift integration to export data from many Salesforce instances. The activity ran between 8 and 18 August 2025. All Drift tokens were revoked on 20 August 2025.

What is going on

An OAuth token is a digital pass that lets one app talk to another on your behalf. When you connect a chat tool like Drift to Salesforce, Salesforce issues that pass so the chat tool can read and write records. The pass works without a password and without a login prompt.

Think of it as a spare key you give a cleaning service. If someone steals the key from the cleaner, the front door still opens normally and nothing looks broken.

That is what happened here. With the stolen tokens, the attacker exported large amounts of Salesforce data, then searched the results for AWS keys, Snowflake tokens and passwords. Secrets that staff had pasted into support cases or notes were the prize, not the sales records themselves.

Who is affected

The direct impact falls on organisations that had the Salesloft Drift integration connected to Salesforce during that window. Revoking the tokens stopped further access, but any data already exported stays in the attacker's hands.

The wider lesson reaches further. Any business that has connected third-party SaaS apps to Salesforce or Google Workspace carries the same kind of exposure, because the risk sits with the connected app, not with your own website or login page.

What to do now

  1. Rotate the credentials stored in your CRM. Any AWS key, database token or password that appears in a case, note or attachment should be revoked and reissued.
  2. Review your connected apps. In Salesforce and Google Workspace, list every third-party app with access and remove the ones you no longer use.
  3. Tighten the scopes. Give each remaining app the narrowest permissions it needs, and add IP restrictions so tokens only work from expected addresses.
  4. Search your CRM data for secrets. Look for keys and passwords in free-text fields, then tell staff to stop pasting them there.
  5. Check your access logs for unusual bulk exports during and after the 8 to 18 August 2025 window.

How to check your own site

This incident did not come through your website, but the same habit of leaving credentials in places they do not belong affects websites too. The free Website Security Check reviews outdated CMS versions, known-vulnerable plugins, missing security headers, weak TLS and email-authentication gaps. If you want exposed-file and secret checks on a site you own and have verified, you can run a full scan.

Source: Google Cloud threat intelligence, August 2025.