# Recent cloud security breaches in the ledger, 2025 to November 2026

Facts read 16 Nov 2026. Page reviewed 16 Nov 2026.

Eight ledger entries were disclosed between March 2025 and August 2026, from the Salesforce vishing campaign to IEH Corporation's Form 8-K of 6 August 2026. Each is listed with its date, the source and the access path the source describes. Read 16 Nov 2026.

## Eight entries from 2025 and 2026, newest first

Each row gives the date, the organization, what its primary source says about access, and the path the ledger assigns. The source is named in the second column and linked in the list below.

| Disclosed | Organization | What the source says about access | Access path |
| --- | --- | --- | --- |
| Aug 6, 2026 | IEH Corporation (Form 8-K) | A phishing email carried a link disguised as a Microsoft document-sharing link; the user entered Microsoft 365 credentials into a fraudulent login page. One employee's mailbox was affected; the filing says no evidence currently exists of exfiltration. | stolen-user-credentials |
| Jun 23, 2026 | 8x8, Inc. (Form 8-K) | An unauthorized third party exploited the Klue third-party integration connected to the company's Salesforce system on June 11 and 12, 2026. | third-party-access |
| Nov 27, 2025 | Mixpanel (company post) | The company detected a smishing campaign on November 8, 2025 and revoked sessions and rotated credentials for impacted accounts. Data exposed: not public. | stolen-user-credentials |
| Sep 2, 2025 | Cloudflare (company post) | The actor used OAuth credentials tied to the Salesloft Drift chat agent's Salesforce integration; 104 Cloudflare API tokens were found in the case data. | third-party-access |
| Aug 26, 2025 | Nx (post-mortem) | A GitHub Actions injection vulnerability was used to steal an npm publishing token; malicious packages were live for 4 hours. | leaked-access-key |
| Aug 20, 2025 | Salesloft (Drift) | The actor reached the Salesloft GitHub account, then Drift's AWS environment, and took OAuth tokens for customers' integrations. | leaked-access-key |
| Jul 23, 2025 | Amazon Web Services (bulletin) | An inappropriately scoped GitHub token in a build configuration let the actor commit malicious code to an extension repository. | over-permissioned-identity |
| Mar 12, 2025 | Salesforce customers (Salesforce post) | Callers impersonating IT support led employees to phishing pages or to add a malicious connected app; counts not public. | stolen-user-credentials |

## The two 2025 integration incidents share one root in Salesloft's report

Cloudflare's post and Salesloft's investigation summary describe the same event from two sides. Salesloft says the actor used tokens taken from Drift's AWS environment; Cloudflare says it was among the customers whose Salesforce tenant was accessed with a stolen credential used by the Salesloft integration, and that the access ran from August 9 to 17, 2025 (Cloudflare and Salesloft, read 16 Nov 2026). The ledger lists both because each organization published its own statement, and it classes the supplier's entry by how the supplier was reached and the customer's by how the customer was reached.

## The 2026 entries are filings, which state less

The two 2026 entries come from SEC Form 8-K filings. A filing records what the company chose to report: 8x8 reported fragmented contract and opportunity information, sales team notes and customer contact details, and said it and Klue, with support from Salesforce, disabled the integration. IEH reported that the affected mailbox held email messages, attachments, customer communications, purchase orders and engineering documentation. Neither filing gives a number of affected individuals; that field reads not public.

## Reading the list

Among these eight entries, three are stolen-user-credentials, two are third-party-access, two are leaked-access-key and one is over-permissioned-identity. None is classed public-resource, cross-tenant, exposed-network-service or retained-access. That is a count of entries read for this edition, not a measure of how common each path is. New entries are added when a company statement, regulator filing, court document or provider post-mortem is found and read.

## Related pages

- [Cloud Misconfiguration Breaches in the Ledger](/cloud-misconfiguration-breaches/)
- [Snowflake Data Breach: What the Filings Say](/snowflake-data-breach/)
- [Capital One Breach: Company Statement and OCC Order](/capital-one-breach/)
- [All of them](/guides/)

## Sources

- IEH Corporation, Form 8-K: https://www.sec.gov/Archives/edgar/data/50292/000117494726000761/form8k-36187_iehc.htm (read 16 Nov 2026)
- 8x8, Inc., Form 8-K, Item 1.05: https://www.sec.gov/Archives/edgar/data/1023731/000102373126000084/eght-20260617.htm (read 16 Nov 2026)
- Mixpanel, SMS security incident: https://mixpanel.com/blog/sms-security-incident/ (read 16 Nov 2026)
- Cloudflare, response to the Salesloft Drift incident: https://blog.cloudflare.com/response-to-salesloft-drift-incident/ (read 16 Nov 2026)
- Nx, s1ngularity post-mortem: https://nx.dev/blog/s1ngularity-postmortem (read 16 Nov 2026)
- Salesloft, Drift security update: https://trust.salesloft.com/?uid=Drift+Security+Update (read 16 Nov 2026)
- AWS security bulletin AWS-2025-015: https://aws.amazon.com/security/security-bulletins/AWS-2025-015/ (read 16 Nov 2026)
- Salesforce, protect against social engineering: https://www.salesforce.com/blog/protect-against-social-engineering/ (read 16 Nov 2026)

Last reviewed 16 Nov 2026. Canonical: https://cloudsecuritybreaches.com/recent-cloud-security-breaches/
