Stripe account hacked? Here’s what to do
Move fast and in the right order: reclaim the account through Stripe’s official flow, kick the attacker out of every session, then close the door they came through — usually a password that leaked in a breach and was reused.
The Stripe data on that forum came out of shops’ accounts, not out of Stripe
If you have run into a headline about a Stripe data breach since 18 August 2026, here is the part the headline leaves out. What leaked was a pile of secret API keys belonging to individual shops, and the customer data was then pulled out through Stripe’s ordinary interface using those keys. The analysis by Ransomnews, covered by Security Affairs, Cybernews and CyberSecurityNews between 18 and 20 August, describes roughly 35 GB of exports covering 659 merchant accounts and about 688,000 customer records across 42 countries. None of the reporting describes a break-in at Stripe itself. For a shopper that means there is no Stripe password of yours to reset, because you almost certainly do not have one. What there is, is a stack of genuine order details sitting in strangers’ hands, which is a scam problem rather than a login problem.
Stripe’s own documentation on API keys (for shop owners)
Analysis by Ransomnews, published 18–19 August 2026. Reported by Security Affairs, Cybernews, CyberSecurityNews and gbhackers between 18 and 20 August 2026.
If your Stripe account was hacked: start recovery at the official page (support.stripe.com/), change the password to a unique one, sign out all other sessions, and re-check the recovery email and phone on the account. Then find out how the attacker got in — check whether your password appears in known breach data — and turn on two-factor authentication so it can’t happen again.
Recover your Stripe account, step by step
These steps follow Stripe’s official process. Official links only: account recovery · password reset.
Go through your card and bank statements for the last three months line by line, including the small amounts. Test charges of a dollar or two are how somebody checks whether a card still works before spending properly.
Turn on instant transaction alerts in your banking app if they are not already on. It is the cheapest early-warning system there is, and it does not depend on anyone notifying you that a shop you used was involved.
Go into the shops you buy from rarely and delete the saved cards. A stored card at a small store you used twice in 2024 is exposure with no convenience attached to it.
Treat email about refunds, receipts and delivery problems as suspect for the next few weeks, especially the ones that get your order right. Open the shop’s site yourself rather than any link, and check the order from inside your account.
If you find a charge you did not make, dispute it with your card issuer as unauthorised and ask for a replacement card number. Telling the shop is worth doing too, but the bank runs its own process on its own clock and that is the one that gets your money back.
If you run a business on Stripe: roll every live secret key from the dashboard, read the API request and payout settings logs for activity that is not yours, replace broad keys with restricted ones, and check that the bank account on your payouts is still your own.
What trips people up with Stripe
- Check what you are actually reacting to before you do anything. The reporting describes secret keys belonging to individual shops, obtained from public code repositories, exposed configuration files, build logs and malware on developers’ machines, then used against Stripe’s normal API. That is a very different thing from somebody getting inside the payment company, and it changes who can help you: the shop and your bank can, Stripe cannot, because you are not its customer.
- The numbers in the coverage do not agree with each other, and chasing them is a waste of your afternoon. One count puts it at 659 merchant accounts with live keys, another at 669 folders holding 1,033 keys of varying freshness. What nobody has published is the list of shops, so there is no way to look yourself up. Work from your own card statements instead, which is the one record you can actually check.
- Your card number is not the thing to worry about here. Stripe’s API does not hand back full card numbers, so what an export like this carries about a payment is the brand, the last four digits and the expiry, sitting next to your name, email address and billing address. The valuable part for whoever downloaded it is knowing exactly what you bought, for how much and on what day.
- That order history is what makes the follow-up convincing. A refund offer, a failed-payment notice or a delivery problem that quotes your real purchase back at you does not read like a scam, which is the whole point of stealing receipts rather than card numbers. Nobody legitimate needs you to re-enter card details through a link in a message about an order you already paid for.
- If you sell through Stripe rather than buy through it, the key is only half the job. Rotating a live secret key does nothing about the copy still sitting in your git history, in an old build log or in a container image, and researchers found working keys in all three places. Roll the key, then go and find where it leaked from, or you will be doing this again.
Was Stripe hacked, or was it the shops that use it?
It was the shops. On 18 August 2026 a seller on a cybercrime forum published, for free rather than for money, a dataset of about 35 GB spread across roughly 17,654 files. Researchers at Ransomnews went through it and found live secret API keys for 659 merchant accounts, with something in the order of 688,000 customer records exported through them, from businesses in 42 countries. Security Affairs, Cybernews, CyberSecurityNews and gbhackers all covered the analysis between 18 and 20 August, and all of them landed on the same conclusion about where it came from.
The keys did not come from Stripe. They came from the places developers keep leaving them: hardcoded in public code repositories, sitting in configuration files on servers nobody locked down, printed into build logs that were never masked, and lifted off working machines by information-stealing malware. Ransomnews put the wider scale of that at more than 50,000 Stripe secrets discoverable in public code and on misconfigured servers, of which a meaningful share still worked, and reported that a live key they tested could be used within seventeen hours of exposure. Once somebody holds a shop’s secret key, they do not need to break anything: they ask Stripe’s API for that shop’s customers, charges and invoices, and it answers, because from the outside the request looks exactly like the shop asking.
What that leaves for a shopper is narrower than the headlines suggest, and more annoying than they let on. The exports are the payment objects a shop can normally read: customers, charges, payment intents, checkout sessions, invoices, refunds, disputes and subscriptions. So the record of you includes your name, your email address, your billing address, what you bought and when, and the brand, last four digits and expiry of the card, but not a usable card number. Stripe has not published a consumer notice about the dataset and no list of affected shops exists publicly, so if a notification reaches you at all it will come from the store you bought from. Until then the sensible reading is that somebody may hold your receipts, and receipts are what make a fake refund email work.
Got a "new login" alert from Stripe?
Treat it as real but verify it the safe way: never tap the link in the message itself (fake login alerts are a top phishing template for Stripe). Open the app or type the address yourself, check the active-sessions list in security settings, and if you see a device or location you don't recognize, sign it out and change your password immediately. If the alert was genuine, that password is burned — assume it's circulating and change it everywhere else you reused it.
Still logged in? Lock the account down now
If you can still get in, you're racing the attacker. In this order: change the password to a long, unique one; sign out all other sessions/devices (the setting exists in Stripe's security settings); confirm the recovery email and phone number are yours (attackers quietly add their own so they can "recover" the account later); remove unfamiliar linked apps or API access; and turn on two-factor authentication. Only then deal with anything the attacker posted, sent or bought.
Locked out of Stripe — email or phone was changed
This is the worst-case scenario and the most common complaint: the attacker changed the account email, phone number or password so the normal reset flow emails them, not you. Do NOT keep triggering password resets — they go to the hacker. Go straight to Stripe's dedicated recovery flow (link above), which is built for exactly this case: it verifies you by your original signup details, previous passwords, linked devices or a government ID / selfie check, bypassing the stolen email. Watch for the security notice Stripe sent to your OLD email when the address was changed — it usually contains a "revert this change" link that works for a limited time and is the fastest way back in.
The attacker spent, moved or stole money
Report the unauthorized transactions to Stripe through the official flow the moment you're back in (or even before — fraud reports don't require account access). U.S. consumer protections for electronic transfers generally limit your liability the faster you report, so speed matters more than completeness. Also call the bank or card issuer behind the funding source — they can dispute, reverse or block further charges — and file at reportfraud.ftc.gov so the pattern is on record.
Why this happened — and how to make sure it can’t again
About a third of account takeovers are credential stuffing: a password you used on Stripe (or the email behind it) leaked in some other company’s breach, and attackers replayed it here automatically. The FBI’s IC3 logged over 5,100 account-takeover complaints with $262M in losses in 2025 alone (IC3). Even when Stripe itself was never breached, your reused password from another site opens it.
So after recovery, check what’s already out there: our free scanner shows which known breaches and dark-web dumps include your email — and whether passwords were exposed with it.
Check my exposure — free →After you recover: three doors to close
- Unique password + 2FA. A password manager plus app-based two-factor stops both stuffing and phishing replays.
- Reset everywhere you reused that password — email first (it’s the master key), then bank, then the rest.
- Shrink your public footprint. Attackers research targets on data-broker sites (your address, phone, relatives — enough to social-engineer support lines). Our free opt-out guide covers 190 of them, step by step.
Hacked Stripe account, answered
How did my Stripe account get hacked?
The most common cause isn't a hack of Stripe itself — it's credential stuffing: a password you used on Stripe leaked from some other site's breach, and attackers tried it here automatically. Roughly a third of account takeovers happen this way, with phishing (fake Stripe login pages and alerts) close behind. That's why the first fix is a unique password, not just a new one.
Can I get my Stripe account back?
Usually yes. Use the official recovery flow (https://support.stripe.com/) — it can verify you even when the attacker changed the email and password. Be patient and respond quickly to follow-ups so the case stays open.
Should I just make a new Stripe account instead?
Not until you've tried recovery. The old account keeps your history and contacts — and while the attacker controls it, it will be used to scam people who trust you. Recover it, or at minimum report it as compromised so Stripe can lock it, before you start over.
Will I get money back that was stolen through my Stripe account?
Often, if you move fast. Report the unauthorized activity to Stripe and to the bank or card behind it — U.S. protections for unauthorized electronic transfers generally limit your losses the sooner you report. Peer-to-peer payments you were tricked into sending yourself are much harder to recover than transactions the attacker made — another reason to report the takeover itself, with evidence.
Was Stripe hacked in August 2026?
Not according to the people who examined the data. The dataset published on 18 August 2026 contained secret API keys belonging to individual merchants, and the customer records in it were exported through Stripe’s normal interface using those keys. Reporting from Security Affairs, Cybernews and CyberSecurityNews describes the keys as having leaked from the merchants’ own code, servers and machines rather than from Stripe.
Were credit card numbers exposed in the Stripe merchant key leak?
Full card numbers are not something Stripe’s API returns, so an export built from it carries the card brand, the last four digits and the expiry date rather than a number anyone can spend. What it does carry is your name, email address, billing address and a detailed record of what you bought. That combination is worth more for impersonating a shop in an email than it is for cloning a card.
How do I know whether a shop I bought from was affected?
At the moment you cannot, because no list of the affected merchants has been published and Stripe has issued no consumer notice about the dataset. The practical substitute is your own statement: read the last ninety days of card charges, switch on transaction alerts, and treat any message about a refund or a delivery problem with unusual suspicion, particularly the ones that quote a real order correctly.
Do I need to change my Stripe password?
Only if you actually have a Stripe account, which means you sell something rather than buy it. Shoppers do not have logins with Stripe, they have logins with the shops, and it is those accounts and the cards saved inside them that are worth tidying up. If you do run a business on Stripe, the password is secondary to rolling your live secret API keys and reading the request logs.
I see a charge from STRIPE on my statement that I do not recognise. What is it?
Usually it is a legitimate purchase wearing the processor’s name instead of the shop’s, which happens when a small business has not set its own statement descriptor. Look through your email for a receipt around the same date and amount before assuming fraud. If nothing matches, dispute it with your bank, and be aware that searching for a Stripe support phone number tends to surface fake ones run by scammers.
I run a shop on Stripe. What should I do first?
Roll every live secret key in the dashboard, then work out where the old one leaked from, because a key that is in your git history or an old build log will simply leak again. After that, read the API request logs and the payout settings for anything you did not do, replace broad keys with restricted ones scoped to what each integration actually needs, and check that the bank account receiving your payouts is still yours.
How do I stop my Stripe account being hacked again?
Three things close most of the doors: a unique password (a manager makes this painless), app-based two-factor authentication, and shrinking your exposed footprint — checking your email against known breach databases and removing your personal data from data-broker sites that attackers use to research targets.