Klue breach: how a forgotten credential exposed customers' data
Key takeaways
- Huntress says the attacker used a long-disused but still active credential that Klue had created to prototype an integration it later abandoned.
- The attackers pushed a code update to Klue capable of collecting the OAuth tokens customers use to connect Klue to their own systems.
- Those stolen tokens were used to query customers' CRM tools directly and exfiltrate data.
- Huntress says the data taken from its Salesforce was sales and contact data, with no product, telemetry, password or payment card data affected.
- Revoking integrations may not be enough after token theft; Huntress recommends considering revoking all active sessions for affected services.
In June 2026, attackers stole CRM data from customers of Klue, a market intelligence platform, without breaking into those customers directly. Huntress, one of the companies affected, published a detailed account of how it happened. The starting point was not a new vulnerability. It was an old credential nobody had switched off.
How the chain worked
According to Huntress, Klue's compromise began on 11 June, with anomalous behaviour in a system that connects to various integrations with other software platforms. Huntress now understands that the attacker used a long-disused but still active credential, originally created by Klue to prototype a third-party integration it later abandoned.
From there the attacker pivoted into Klue's infrastructure and pushed a code update capable of collecting the OAuth tokens that Klue's customers use to connect Klue to their own systems. With those tokens, the attacker queried customers' CRM tools directly and exfiltrated the data. Huntress calls it a security domino effect: one compromise leading to a chain of follow-on compromises.
Klue became aware of the anomalous behaviour the following day, Huntress says. It deactivated the OAuth credentials for all customers, temporarily disabled its integrations, removed the token-theft code and issued a general alert to customers on 13 June.
The extortion that followed
On 16 June, some Huntress staff received emails with the subject line "top secret email" warning that their data had been downloaded and giving 48 hours to respond. Huntress suggested a threat actor named Icarus might be responsible; Icarus later listed Klue on its leak site, claiming the attack, and on 22 June listed data for Huntress and several other affected companies.
Huntress says the files relating to it are limited to Salesforce data: business contact details, business names, products trialled or used, subscription details, sales communications and opportunity notes. It says no data associated with its products or infrastructure, and no telemetry, passwords or payment card data, was affected. Many of the published files, it adds, held only system logs and metadata, because the attackers appear to have bulk-exported everything they could reach.
Huntress also notes that other security vendors, including Recorded Future, Tanium and Jamf, released statements on how they were affected.
What Huntress recommends
For organisations that used Klue, Huntress lists these investigation steps:
- Review logs for known indicators. Cross-reference the indicators Klue provided against logs from Salesforce, Klue and other OAuth applications configured through Klue.
- Request missing logs from vendors. Some services do not make API or access logs readily available.
- Consider revoking active sessions. Because the attack relied on harvested credentials, revoking the integration alone may not be enough.
It also advises against digging through the leaked dataset, since leak archives are often laced with malware, and warns that stolen sales data may be used for phishing that impersonates affected companies. Use trusted, known channels for any communication.
The lesson for everyone else
The detail worth taking away is the first one. The credential that opened the door belonged to an integration Klue had stopped using, but it still worked. Every connected app and integration credential in a business system is a door like that, and an abandoned one is a door nobody is watching.