Skip to content
Cloud Security Breaches

Cloud data breaches: what was exposed, as the companies state it

Company statements and filings read on 16 Nov 2026 give counts that mean different things: about 100 million people at Capital One, roughly 14,000 accounts at 23andMe, 134 customers at Okta, 133 accounts at Mailchimp, 27 accounts at Retool. This page lists each count with what it counts.

Open the ledger ยท All guides

The same word, breach, counts people, accounts, customers and tokens

A count from one incident cannot be set beside a count from another without its unit. Capital One counted individuals. 23andMe counted accessed user accounts and the profiles visible through them. Okta counted customer organizations whose support files were viewed. Cloudflare counted API tokens found in exposed tickets. The table keeps each unit as the source wrote it and does not convert them.

OrganizationCount as statedUnitSource type
Capital One (2019)Approximately 100 million in the United States and approximately 6 million in CanadaIndividuals affectedCompany statement
23andMe (2023)Roughly 14,000 user accounts (less than 0.1% of 14 million customers); about 5.5 million DNA Relatives profiles and about 1.4 million Family Tree profilesAccounts accessed, and profiles seen through themCompany statement
Okta (2023)Files associated with 134 customers; session tokens used to hijack the sessions of 5 customersCustomer organizationsCompany statement
Mailchimp (2023)133 accountsAccountsCompany statement
Retool (2023)27 cloud customer accountsAccounts taken overCompany statement
Cloudflare (2025)104 Cloudflare API tokens found in the exposed case dataTokensCompany statement
Microsoft (2023)Approximately 25 organizations in the public cloud, including government agenciesOrganizations with email accessedProvider post-mortem

Exposure is stated by data type, and some types are not public

The 23andMe statement says the actor reached the 14,000 accounts using usernames and passwords that were also used on other websites, and that profile information in the connected relative features was visible through them (23andMe, read 16 Nov 2026). Mailchimp, the Intuit subsidiary, wrote that it found no evidence that Intuit systems or customer data beyond the 133 accounts were affected (Mailchimp, read 16 Nov 2026).

Some filings give no data description at all. Advance Auto Parts' Form 8-K says only that some files contain personal information including Social Security numbers of current and former applicants and employees. AT&T's Form 8-K says the call and text records did not include content or Social Security numbers. Mixpanel's November 2025 statement lists no counts, and the ledger records the exposed field as not public.

Some exposures were internal data, and the company said so

Not every ledger entry involves customer records. Microsoft's September 2023 post on an overly permissive storage token says the exposed data included backups of two former employees' workstation profiles and internal Teams messages, and that no customer data was exposed (Microsoft, read 16 Nov 2026). Cloudflare's February 2024 post says the actor reached documentation and a limited amount of source code on its self-hosted Atlassian server, using an access token and three service account credentials it had not rotated after the October 2023 Okta compromise (Cloudflare, read 16 Nov 2026).

These entries stay in the ledger because the access path, a leaked key or unrotated credential, matches the paths in customer-data incidents.

What the counts leave out

Counts are the companies' own, as of the date each statement was made, and several were revised. Capital One reported on February 22, 2021 that it found about 4,700 additional Social Security numbers among data already accessed. The ledger does not total the counts, because a total of individuals, accounts and tokens would not describe any single thing.

Sources

  1. Capital One, Information on the Capital One cyber incident, read 16 Nov 2026
  2. 23andMe, Addressing Data Security Concerns, read 16 Nov 2026
  3. Okta, root cause of unauthorized access to the support case management system, read 16 Nov 2026
  4. Mailchimp, January 2023 security incident, read 16 Nov 2026
  5. Retool, MFA isn't MFA, read 16 Nov 2026
  6. Cloudflare, response to the Salesloft Drift incident, read 16 Nov 2026
  7. Cloudflare, Thanksgiving 2023 security incident, read 16 Nov 2026
  8. Microsoft MSRC, Storm-0558, read 16 Nov 2026
  9. Microsoft MSRC, overly permissive SAS token, read 16 Nov 2026
  10. Mixpanel, SMS security incident, read 16 Nov 2026

Last reviewed 16 Nov 2026.