As cited
Copy frozen at (site build).
breaches incidents
KlueセキュリティインシデントとRecorded Futureへの影響
Recorded Future experienced an incident on June 12-13, 2026, affecting its Salesforce account through a compromised OAuth token in an integration layer between Salesforce and Klue, a third-party marketing vendor. The breach did not target Recorded Future directly; rather, the company was incidentally exposed when attackers exploited the Klue-Salesforce integration. The exposed data was limited to business contact information and customer names stored in the Salesforce database, while Recorded Future's core platform, Intelligence Graph, and internal systems remained unaffected.
Why it matters: Recorded Future customers and partners should review their own exposure to the Klue ecosystem and monitor for phishing or spam; organizations integrating SaaS platforms should evaluate third-party integration security as part of overall SaaS security posture management.
- Source published
- First seen by Cybersecurity Tracker
Source attribution
Correction
Correction recorded as of .
breaches incidents
KlueセキュリティインシデントとRecorded Futureへの影響
No summary had been written when this copy was frozen.
- First seen by Cybersecurity Tracker
Source attribution
Correction
Correction recorded as of .
breaches incidents
KlueセキュリティインシデントとRecorded Futureへの影響
Recorded Future disclosed that Klue, a third-party marketing vendor, suffered unauthorized access to an integration layer connecting Klue with other SaaS platforms including Salesforce. Recorded Future's Salesforce account was affected through a compromised OAuth token, exposing business data fields such as customer contact names, email addresses, and potentially certain business contract information, though the company's core platform and internal databases were not accessed. Recorded Future has revoked related OAuth tokens, engaged with Salesforce for investigation support, and is monitoring for further anomalous activity.
Why it matters: Recorded Future customers should review potential exposure through the Klue ecosystem and implement standard phishing and spam defenses; organizations using Klue or similar third-party integrations with Salesforce should audit their own OAuth token management and SaaS application access controls.
- Source published
- First seen by Cybersecurity Tracker