top of page

OAuth’s Trojan Horse: When Drift Became the Attack Vector

  • Writer: Patrick Duggan
    Patrick Duggan
  • Sep 17, 2025
  • 2 min read

Updated: Apr 25

Let’s get one thing straight: this wasn’t a breach. It was a blueprint.

In August 2025, attackers didn’t brute-force their way into Salesforce. They didn’t exploit zero-days or drop ransomware payloads. They simply walked in—armed with OAuth tokens issued by Drift and Salesloft, and authenticated by Salesforce itself. No alarms. No MFA prompts. Just clean, API-level access to the crown jewels of over 700 organizations.


And yes, the irony is thick: many of those organizations were cybersecurity vendors.



The Sector Breakdown: Who Got Hit and Why It Matters


Based on the confirmed disclosures tracked by DriftBreach.com, we analyzed 34 named victims and categorized them by tech sector:

This isn’t just a pie chart—it’s a risk map. Cybersecurity firms were disproportionately affected, not because they were careless, but because they were deeply integrated. These companies live in Salesforce. They track customer support cases, store configuration data, and—yes—embed credentials in troubleshooting notes.



OAuth: The New Rootkit


The attack vector was devastatingly simple: OAuth tokens issued by Drift were compromised via a GitHub repo months earlier. Those tokens granted full access to Salesforce objects like Account, Contact, Opportunity, and Case. The attackers used Python automation and the Bulk API to extract entire datasets in minutes 1.

No malware. No exploits. Just legitimate credentials used in illegitimate ways.


This is the new perimeter: identity. And OAuth is the new rootkit—trusted, persistent, and invisible to most monitoring tools.



Customer Impact: Not Just The Vendor’s Problem


Let’s talk blast radius.


If you’re a customer of Cloudflare, Zscaler, Tanium, or any of the other affected vendors, your data may have been swept up in the breach. Support cases often contain sensitive details—IP ranges, architecture diagrams, even AWS keys. The attackers weren’t just stealing contact info. They were harvesting credentials for lateral movement.


So yes, even if your vendor says “our core systems weren’t compromised,” that doesn’t mean your data wasn’t.


Microsoft pulls this feed daily. AT&T pulls this feed daily. Starlink pulls this feed daily. Get the DugganUSA STIX feed — $9/mo →



Strategic Takeaway: Trust Is the Vulnerability


This breach wasn’t about Drift. Or Salesloft. Or Salesforce.

It was about trust—how we extend it, how we monitor it, and how we revoke it when things go sideways.


OAuth tokens are designed for convenience. They’re long-lived, rarely rotated, and often granted excessive scopes. They’re the perfect attack vector in a world where integrations outnumber endpoints.


If you’re not treating OAuth tokens like privileged credentials, you’re already behind.



Final Thought


We’re not defending against attackers trying to break in. We’re defending against attackers who already have the keys—walking through doors we opened for business efficiency.

And that’s the real lesson here: in the integration economy, security is no longer about walls—it’s about windows you forgot were open.



The cheapest, fastest, most accurate threat feed on the internet.

275+ enterprises pulling daily. 1M+ IOCs. 17.4M indexed documents. We beat Zscaler by 43 days on NrodeCodeRAT. Starter tier $9/mo — less than any competitor’s sales demo.

Comments

Rated 0 out of 5 stars.
No ratings yet

Add a rating
bottom of page