Publicly Exposed Stripe API Keys Leaked for Hundreds of Merchant Accounts
Breach & Incident Intelligence · 6 sources · Updated 3mo ago · First seen Aug 19, 2026

A leaked dataset posted on an illicit forum exposed live Stripe API keys and related payment data from hundreds of merchants, with reports citing 659 to 669 vendor accounts, 1,033 confirmed keys in the initial release, and claims that the broader cache could contain up to 20,000 to 50,000 Stripe secrets. Researchers said the material included customer records, invoices, transaction metadata, hosted invoice links, promotional codes, partial payment card details, and roughly 33 GB to 35 GB of associated data, creating risks of fraud, privacy violations, unauthorized refunds, payment rerouting, and revenue loss.
Investigations indicate Stripe itself was not breached; instead, the exposed credentials appear to have been harvested from merchants’ public code repositories, unmasked GitHub Actions logs, misconfigured web servers, exposed environment files, or debug logs. Analysts verified that some sampled keys were still active and could be used to list customer data, create fraudulent payment links, modify webhooks, and even process test charges, while some merchants reportedly rotated keys without revoking old ones. Recommended response measures include auditing version-control history, revoking and rotating exposed keys, replacing broad secrets with restricted Stripe keys, and enabling Stripe fraud-detection controls such as Radar rules.


