Snyk: Third-Party Vendor Security Incident (Klue)
Affected components: SNYK-EU-01 (app.eu.snyk.io) - Snyk LearnSnyk LearnSnyk IaCSNYK-US-01 (app.snyk.io) - Snyk IaCSNYK-GOV-01 (app.snykgov.io) - Snyk Open SourceSnyk Open SourceSnyk AppRiskSNYK-AU-01 (app.au.snyk.io) - Snyk AppRiskSnyk Open SourceSNYK-US-02 (app.us.snyk.io) - Snyk Open SourceSNYK-AU-01 (app.au.snyk.io) - Snyk ContainerSnyk ContainerSnyk LearnSNYK-US-02 (app.us.snyk.io) - Snyk LearnEvo by SnykSNYK-US-02 (app.us.snyk.io) - Evo by SnykSNYK-AU-01 (app.au.snyk.io) - Snyk CodeSnyk CodeSnyk IaCSNYK-US-02 (app.us.snyk.io) - Snyk IaCSNYK-AU-01 (app.au.snyk.io) - Snyk LearnSnyk LearnSNYK-EU-01 (app.eu.snyk.io) - Snyk IaCSnyk IaCEvo by SnykSNYK-US-01 (app.snyk.io) - Evo by SnykSnyk AppRiskSNYK-EU-01 (app.eu.snyk.io) - Snyk AppRiskSnyk CodeSNYK-EU-01 (app.eu.snyk.io) - Snyk CodeSnyk LearnSNYK-US-01 (app.snyk.io) - Snyk LearnSnyk Support (support.snyk.io) - Support PortalSupport PortalSNYK-EU-01 (app.eu.snyk.io) - Snyk Open SourceSnyk Open SourceSnyk ContainerSNYK-US-01 (app.snyk.io) - Snyk ContainerEvo by SnykSNYK-AU-01 (app.au.snyk.io) - Evo by SnykSnyk Open SourceSNYK-US-01 (app.snyk.io) - Snyk Open SourceSNYK-AU-01 (app.au.snyk.io) - Snyk Open SourceSnyk Open SourceSnyk ContainerSNYK-GOV-01 (app.snykgov.io) - Snyk ContainerSnyk AppRiskSNYK-US-01 (app.snyk.io) - Snyk AppRiskSNYK-AU-01 (app.au.snyk.io) - Snyk IaCSnyk IaCSnyk ContainerSNYK-EU-01 (app.eu.snyk.io) - Snyk ContainerSNYK-GOV-01 (app.snykgov.io) - Snyk IaCSnyk IaCSnyk AppRiskSNYK-US-02 (app.us.snyk.io) - Snyk AppRiskSnyk ContainerSNYK-US-02 (app.us.snyk.io) - Snyk ContainerEvo by SnykSNYK-EU-01 (app.eu.snyk.io) - Evo by SnykSnyk CodeSNYK-US-02 (app.us.snyk.io) - Snyk CodeSnyk CodeSNYK-US-01 (app.snyk.io) - Snyk CodeSnyk CodeSNYK-GOV-01 (app.snykgov.io) - Snyk Code
Timeline of updates
- investigating
We were notified of a security incident involving Klue, a market intelligence platform used by Snyk and a wide range of companies for competitive intelligence. An unauthorized party accessed data from Snyk's Salesforce environment through Klue's integration. Other security vendors, such as Recorded Future (https://www.recordedfuture.com/blog/klue-security-incident), Tanium (https://www.tanium.com/blog/security-update-taniums-response-to-the-klue-breach-that-allowed-data-exfiltration-from-salesforce/), Huntress (https://www.huntress.com/blog/klue-breach-investigation), and Jamf (https://www.jamf.com/blog/klue-incident/) have been impacted and have shared updates publicly. Our investigation shows that, to our knowledge at this point in time, the impact was primarily limited to business data fields within the Salesforce environments. This includes customer business contact information and only the title and description from a limited subset of customer support cases. The body or contents of the support cases were not included nor did it affect Snyk's products. There was no impact on our ability to serve our customers. Snyk's platform, services, and infrastructure remain fully operational and were not involved. Upon notification from Klue, we promptly disabled the Klue integration in Salesforce and began our own review. We will post updates here as we learn more.
- monitoring
We were notified of a security incident involving Klue, a market intelligence platform used by Snyk and a wide range of companies for competitive intelligence. An unauthorized party accessed data from Snyk's Salesforce environment through Klue's integration. Other security vendors, such as Recorded Future, Tanium, Huntress, and Jamf have been impacted and have shared updates publicly. Our investigation shows that, to our knowledge at this point in time, the impact was primarily limited to business data fields within the Salesforce environments. This includes customer business contact information and only the title and description from a limited subset of customer support cases. The body or contents of the support cases were not included nor did it affect Snyk's products. There was no impact on our ability to serve our customers. Snyk's platform, services, and infrastructure remain fully operational and were not involved. Upon notification from Klue, we promptly disabled the Klue integration in Salesforce and began our own review. We will post updates here as we learn more.
- resolved
Our forensic investigation into the June 2026 Klue/Salesforce incident, conducted in partnership with Mandiant, is now complete. The investigation confirmed that the impact was limited to business CRM data. No evidence of impact to the Snyk platform, and any sensitive data within, was found. All impacted customers were notified directly and the data involved is consistent with what was disclosed in our June 22 blog post (https://snyk.io/blog/when-a-vendors-breach-becomes-yours-lessons-from-the-klue-incident/).
Impact, status and times are the vendor’s own, as last archived. View on stspg.io (opens in new tab). Snyk profile · Recent Snyk incidents · Markdown · JSON