Agent incident · Sep 8, 2026

Salesloft Drift. The access path.

Stolen OAuth tokens exported Salesforce data from hundreds of orgs. How compromised OAuth tokens turned a SaaS integration into a path to sensitive data.

drift-oauth-tokenstolen; scoped to read/query SalesforceEntry
salesforce-orgaccess depends on each stolen token’s scope
SOQL bulk exportpull everything the token can seeReached
SEP 8, 2026

The record

Entry point. drift-oauth-token, stolen; scoped to read/query Salesforce.

The identity in the middle. The Drift OAuth token held by each affected organisation, scoped to read and query Salesforce.

What was reached. Salesforce data exported from each affected org.

AT A GLANCE

Stolen OAuth tokens exported Salesforce data from hundreds of orgs.

PATH

The path, step by step.

Taken from the published reporting. Nothing here is reconstructed.

StepRole in the pathWhat the reporting records
drift-oauth-tokenEntrystolen; scoped to read/query Salesforce
salesforce-orgStepaccess depends on each stolen token’s scope
SOQL bulk exportReachedpull everything the token can see
BREAKPOINT

Where a breakpoint would have been

The scope on each token. The breach happened at the vendor, but what each organisation lost was decided locally, by how much the integration had been allowed to see.

A breakpoint is the single change that closes a path with the least disruption. Read how that is chosen in the breakpoint page. The full narrative is in the teardown.

ELMOZ ASSESSMENT

3 steps from entry to data.

PRIMARY SOURCES

Where this comes from.

Every field on this page is taken from the published reporting below. The breakpoint assessment is Elmoz reading that path, not a statement about what the affected organisation did.

Google GTIG · The Hacker News, Gainsight · The Hacker News, Klue / Icarus

FAQ

Questions, answered.

The two questions this record answers.

What was the entry point in the Salesloft Drift incident?

The published path starts at drift-oauth-token, stolen; scoped to read/query Salesforce.

What did it reach?

The published path ends at Salesforce data exported from each affected org.

See what your agents can reach. Before someone else does.

Book a demo and we walk through the access paths in an environment like yours.