Klue OAuth breach spreads: 7 firms confirm Salesforce data theft

Key Takeaways

- Klue confirmed attackers stole OAuth tokens on June 12 through a compromised legacy credential, accessing customer Salesforce environments
- Seven companies including Recorded Future, Tanium, Jamf, and Huntress have disclosed data theft from their Salesforce instances
- The Icarus extortion group publicly claimed responsibility and is pressuring victims through the Session messaging platform
The Klue OAuth breach is now a multi-victim incident. Seven enterprise companies have confirmed that attackers stole data from their Salesforce environments after compromising Klue's integration infrastructure. The Icarus extortion group has publicly claimed responsibility.
Klue CEO Jason Smith confirmed the breach this week. On June 12, the company discovered unauthorized activity affecting its integration infrastructure. An attacker exploited a compromised legacy credential tied to an integration service, then used that access to steal OAuth tokens connecting Klue to third-party platforms, particularly Salesforce.
"Our investigation determined that an attacker gained access through a compromised legacy credential associated with an integration service," Smith wrote in a public statement. "The attacker used that access to obtain OAuth tokens used to connect Klue with certain third-party platforms, including Salesforce, and subsequently accessed data within a number of connected customer environments."
Which companies were affected by the Klue breach?
The victim list keeps growing. Recorded Future, Tanium, Jamf, Sprout Social, Gong, Insurity, and Huntress have all disclosed that the breach led to data theft from their Salesforce instances. Most emphasized that the incident did not affect their own platforms, internal systems, or payment data. The attack was confined to CRM data accessible through the compromised OAuth integrations.
Huntress, one of the security firms that investigated the breach, revealed it was also a victim. The stolen data included business contacts, sales communications, pricing information, and other records. That a cybersecurity company fell victim underscores how supply chain attacks through trusted integrations can bypass even security-focused organizations.
How did the OAuth token attack work?
Klue is a competitive intelligence platform that creates "battlecards" for enterprise sales teams. These battlecards help salespeople counter competitor claims during deals. The platform integrates with Salesforce CRM through OAuth tokens, which provide persistent access without requiring repeated logins.
ReliaQuest observed the attackers generating OAuth tokens and using Python scripts to query Salesforce's API for extended periods. The scripts systematically extracted CRM data. Because OAuth tokens grant ongoing access, a single compromised credential can provide an extended window for data exfiltration.
Klue says it immediately revoked affected credentials and tokens, removed unauthorized code, disabled impacted integrations, and engaged CrowdStrike for incident response. The company also notified law enforcement.
Who is the Icarus extortion group?

Icarus is a new extortion operation that has now publicly claimed the Klue attack on its data leak site. "As you've probably already heard, Klue.com has been impacted by us recently. A number of other companies' Salesforce instances, which were partners to Klue, were exfiltrated," the group wrote.
The threat actors are pressuring Klue and affected organizations to contact them through Session, an encrypted messaging platform, to prevent data leaks. BleepingComputer had previously linked the attack to Icarus based on extortion emails sent to affected organizations. Huntress independently confirmed the connection through Session Messenger IDs matching between the extortion emails and the group's leak site.
What should affected organizations do?
Several victim organizations warned that the stolen business contact information could fuel follow-on attacks. Phishing, social engineering, and additional extortion campaigns are likely. Sales data and pricing information could also be valuable for competitors or used to craft convincing business email compromise schemes.
Organizations using Klue should audit their OAuth integrations immediately. Check for unusual API query patterns in Salesforce logs. Review which third-party services hold OAuth tokens to your CRM, and consider whether legacy credentials might still be active.
Klue states there is no evidence that customer content stored directly within the Klue platform was impacted. The breach was limited to third-party integrations. But for enterprises, the distinction matters less than the outcome: their Salesforce data is now in the hands of extortionists.
Logicity's Take
This breach exposes a blind spot in enterprise security: the OAuth tokens connecting SaaS platforms. Companies audit their own infrastructure but rarely inventory which vendors hold persistent access to their CRM. Klue's legacy credential sat dormant until it became an entry point. Expect OAuth token hygiene and vendor integration audits to become standard security practice after incidents like this multiply.
Frequently Asked Questions
What data was stolen in the Klue OAuth breach?
Attackers stole business contacts, sales communications, pricing information, and other CRM records from victim organizations' Salesforce environments. Data stored directly in Klue's platform was not affected.
How did attackers access Klue's integration infrastructure?
Attackers exploited a compromised legacy credential associated with an integration service. They used this access to steal OAuth tokens that connected Klue to customer Salesforce instances.
Who is the Icarus extortion group?
Icarus is a new extortion operation that publicly claimed responsibility for the Klue breach. The group is demanding contact through the Session encrypted messaging platform to prevent data leaks.
Which companies were affected by the Klue breach?
Confirmed victims include Recorded Future, Tanium, Jamf, Sprout Social, Gong, Insurity, and Huntress. All have disclosed Salesforce data theft stemming from the Klue compromise.
Is my Salesforce data at risk if I use Klue?
Klue has revoked affected credentials and tokens. Contact Klue directly to confirm whether your integration was impacted and review your Salesforce API logs for unusual activity.
Another recent vulnerability exposing authentication credentials to attackers
Need Help Implementing This?
If your organization needs to audit OAuth integrations or assess exposure to supply chain attacks through SaaS vendors, Logicity can connect you with security consultants who specialize in enterprise integration security. Contact our team for recommendations.
Source: BleepingComputer
Manaal Khan
Tech & Innovation Writer
Related Articles
Browse all
Kraken Crypto Exchange Extortion: Hackers Threaten to Leak Internal Videos After Insider Breach
Cryptocurrency exchange Kraken is being extorted by hackers who obtained videos of internal systems through bribed support employees. The company says no funds were compromised and refuses to pay, with only about 2,000 accounts affected. Kraken is working with federal law enforcement to prosecute everyone involved.

Windows 11 KB5083769 and KB5082052: April 2026 Patch Tuesday Brings Smart App Control Changes and Security Fixes
Microsoft's April 2026 Patch Tuesday updates are now live for Windows 11, bringing critical security patches alongside a welcome change to Smart App Control. You can finally toggle SAC on or off without wiping your entire system. The updates cover versions 23H2, 24H2, and 25H2.

Zero Trust Identity Security: 5 Ways This Framework Actually Stops Credential Theft
Stolen credentials caused 22% of breaches in 2025, making them the top attack vector. Zero Trust promises to fix this, but only when it's built around identity as the core principle. Here's how organizations can implement it properly.
Open Source PR Backlogs: Why Your GitHub Contribution Sits Unreviewed for a Year
A developer's Jellyfin pull request has been waiting over a year for merge despite two approvals, exposing a systemic crisis in open source maintenance. Queuing theory explains why backlogs grow exponentially, and 60% of maintainers have quit or considered quitting due to burnout.


