klue breach turns stolen oauth tokens into customers' crm data
Attackers used a compromised legacy credential at sales-intelligence vendor Klue to steal the OAuth tokens connecting it to customers' platforms, then pulled data out of those customers' Salesforce and other SaaS accounts.
- affected
- customers that connected Klue Battlecards to Salesforce, HubSpot, Gong and other SaaS platforms
- platforms
- Salesforce, HubSpot, SharePoint, Zoom, Gong, Chorus, Clari, Google Drive, Slack (via Klue integrations)
what happened
- Klue said it identified unauthorized activity in part of its integration infrastructure on June 12, 2026, and that the attacker got in through a compromised legacy credential tied to an integration service.[1]
- The attacker used that access to obtain OAuth tokens connecting Klue to third-party platforms, including Salesforce, then accessed data in connected customer environments. Klue says there is no evidence that content stored in the Klue platform itself was affected.[1]
- FINRA says the stolen tokens covered Klue Battlecards integrations with Salesforce, HubSpot, SharePoint, Zoom, Gong, Chorus, Clari, Google Drive and Slack, and that the attacker bulk-exported CRM data from Salesforce with automated Python scripts.[2]
- According to FINRA, the stolen data included business contact information, support case data and business intelligence reports.[2]
- According to FINRA, Salesforce and Gong disabled the Klue Battlecards integration. Salesforce, as quoted by The Hacker News and GovInfoSecurity, said the issue "is limited to Klue's app connection and does not arise from a vulnerability within the Salesforce platform."[2,3,4]
- FINRA says more than a dozen organizations have confirmed impact, including LastPass, Huntress, Jamf, Tanium, HackerOne, Snyk, OneTrust and BeyondTrust, and that a threat actor identifying itself as Icarus is conducting an ongoing extortion campaign against affected organizations.[2]
- Klue revoked affected credentials and tokens, removed unauthorized code, disabled potentially affected integrations, notified law enforcement and brought in CrowdStrike.[1]
where sources differThe Hacker News wrote that Salesforce disabled the integration in response to an incident at Klue "on June 11, 2026", while Klue and FINRA say Klue identified the activity on June 12, 2026. GovInfoSecurity says the attack first came to light publicly the day before Klue's June 18 post, when Salesforce announced it had suspended the integration. Klue gives no victim count; FINRA says more than a dozen organizations confirmed impact, while TechCrunch reported close to 200 companies affected.
sources5
- 01An Update on the Recent Klue Security Incident ↗ primaryKlueaccessed 2026-10-21
- 02Cybersecurity Alert: Klue OAuth Breach and Salesforce Data Exfiltration ↗ primaryFINRAaccessed 2026-10-21
- 03Salesforce Disables Klue App Integration After OAuth Token Abuse Exposes Customer Data ↗ secondaryThe Hacker Newsaccessed 2026-10-21
- 04Klue confirms OAuth token theft led to Salesforce data heist ↗ secondaryGovInfoSecurityaccessed 2026-10-21
- 05Leaks, data breaches, and ransom notes: The worst hacks of 2026 so far ↗ secondaryTechCrunchaccessed 2026-10-21