Salesforce has revealed that it disabled the Klue Battlecards app integration within its platform in response to a security incident impacting the competitive intelligence company on June 11, 2026.
To that end, organizations will be unable to connect to Salesforce via the app until further notice, the American cloud-based software company noted in an alert published this week.
“Salesforce took this action because our security teams recently detected unusual activity involving the app that may have resulted in unauthorized access to a subset of customer data via the app’s connection to Salesforce,” it noted. “This issue is limited to Klue’s app connection and does not arise from a vulnerability within the Salesforce platform.”
The development comes as an extortion group dubbed Icarus compromised and exfiltrated data from customers of Klue, including cybersecurity company Huntress.
“The data that was copied from our Salesforce account includes business contacts, price quotes, and other sales-related data and messaging,” Huntress said. “No threat data, passwords, payment card information, or engineering data relating to the Huntress agent or telemetry we collect was affected.”
In its own update, Klue said it detected unauthorized activity affecting a portion of Klue’s integration infrastructure on June 12, 2026, adding the attackers gained access through a compromised legacy credential associated with an integration service.
“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,” Klue CEO Jason Smith said. “Based on our investigation to date, the incident was limited to the affected third-party platforms, and there is no evidence that customer content stored within the Klue platform was impacted.”
Specifically, the intrusion is said to have allowed the threat actor to push a code update capable of collecting OAuth tokens that its customers use to connect Klue to their own systems. In response to the breach, Klue has taken steps to revoke affected credentials and tokens, remove unauthorized code, stop remote access, disable potentially impacted integrations, and launch a comprehensive investigation.
As of June 16, 2026, some of Huntress employees have received an email with the subject line “top secret email” and a warning that states: “Your Salesforce data has been downloaded … You have 48 hours to communicate with us. Do the right decision.”
“The threat actor seems to have leveraged a long-disused but still active credential to conduct the initial compromise — one that was originally created by Klue for them to prototype a third-party integration they later abandoned,” the company said. “The threat actor then pivoted into Klue’s infrastructure to steal the tokens used by Klue’s customers, then used those stolen credentials to query those customers’ CRM tools directly and, eventually, to exfiltrate the data.”
Not much is known about the Icarus actor other than the fact that they have been active since April 28, 2026, and have claimed a total of two victims to date. That said, the data theft campaign mirrors prior attack waves mounted by ShinyHunters and UNC6395.
ReliaQuest, in its own analysis of the Klue integration abuse, said the activity shares similarities with the third-party OAuth-abuse playbook associated with the Salesloft Drift and Gainsight compromises that targeted Salesforce environments last year.
“In the attacks we observed, the adversary first authenticated through a compromised Klue integration service account, generated OAuth tokens, and ran automated Python scripts (identifiable by Python-urllib user-agent strings),” ReliaQuest researchers Thassanai McCabe and Alexa Feminella said.
“These scripts first enumerated the org’s object catalog via GET /services/data/v59.0/sobjects, then looped REST API queries against the Salesforce query endpoint (/services/data/v59.0/query) and paginated results via the QueryMore cursor for almost 24 hours.”
These are assessed to be bulk data retrieval actions designed to pull large volumes of CRM records through the Salesforce REST API. This included a “concentrated burst” of nearly a thousand queries in 15 minutes against at least one environment and an extraction window that lasted more than six hours in another case.
It’s unclear how many Salesforce customers were affected by the latest attacks, although Klue said it has been communicating directly with impacted customers, sharing investigative findings, and assisting with their response efforts.
“The common thread is the abuse of OAuth tokens or credentials from a trusted third-party vendor,” ReliaQuest said. “These integrations are non-human identities with persistent, often broad access to sensitive data, yet they are typically monitored far less closely than employee accounts. That gap is why a 24-hour automated query loop could run from a ‘trusted’ integration account without tripping the usual alarms.”
