Data breaches → Operation Endgame 2.0
Was your data in the Operation Endgame 2.0 breach?
2025 · ~15,436,844 accounts exposedCritical severity · 9/10
Operation Endgame 2.0 suffered a data breach in 2025 that exposed around 15,436,844 accounts. If you had an account, some of your personal data may be circulating in leaked databases. The fastest way to know is to check your own email — free, in about 30 seconds, no password required.
What happened
In May 2025, a coalition of law enforcement agencies took down the criminal infrastructure behind the malware used to launch ransomware attacks in a new phase of "Operation Endgame". This followed the first Operation Endgame exercise a year earlier, with the latest action resulting in 15.3M victim email addresses being provided to HIBP by law enforcement. A further 43.8M victim passwords were also provided for HIBP's Pwned Passwords service.
Breach details sourced from Have I Been Pwned, the industry-standard breach database. Risk analysis by Nullivo.
What was exposed, and why it matters
Not all breaches carry the same risk — what matters is which fields leaked. Here is what the Operation Endgame 2.0 breach exposed and what each item actually enables:
Attackers replay leaked passwords across other sites (“credential stuffing”). Because most people reuse passwords, one leak often unlocks email, shopping and banking accounts elsewhere.
Puts you on spam and phishing lists, and confirms to attackers that you hold an account with this service — which makes impersonation emails more believable.
What to do if you were affected
These steps are ordered for this specific breach — the most urgent action given what leaked comes first.
- Passwords: Change this password everywhere you have reused it, starting with your email account — whoever controls your email can reset everything else.
- Email addresses: Treat any message referencing this service with suspicion, and never act on links in unexpected emails.
- Check whether your own email appears in this breach — run a free scan to confirm before you spend time on the steps above.
How urgent is this now?
This breach is recent, so the data is actively traded and the risk is at its highest right now.
Passwords are the reason breach age matters less than people expect. Leaked credentials are compiled into wordlists that get tried against new services for years afterwards, so a password exposed here is unsafe to use anywhere, ever again.
Remember: a breach can't be "un-leaked" — once a database is out, it exists in countless copies. The goal is to make the leaked data useless: change what can be changed, lock down what can't, and remove what has been republished.
Frequently asked questions
What data was exposed in the Operation Endgame 2.0 breach?
The Operation Endgame 2.0 breach exposed passwords, email addresses. Attackers replay leaked passwords across other sites (“credential stuffing”). Because most people reuse passwords, one leak often unlocks email, shopping and banking accounts elsewhere.
How many people were affected by the Operation Endgame 2.0 breach?
Around 15,436,844 accounts were exposed, making it a very large breach by any measure.
What should I do if I had a Operation Endgame 2.0 account?
Change this password everywhere you have reused it, starting with your email account — whoever controls your email can reset everything else. You can check whether your own email appears in this breach with a free Nullivo scan — no password required.
Breaches that exposed similar data
If the Operation Endgame 2.0 breach affected you, these breaches exposed comparable information — worth checking too, since leaked datasets are routinely combined.
- Was your data in the Raaga breach? (2025, ~10,225,145 accounts)
- Was your data in the Canadian Tire breach? (2025, ~38,306,562 accounts)
- Was your data in the Operation Endgame breach? (2024, ~16,466,858 accounts)
- Was your data in the Zacks (2024) breach? (2024, ~11,994,223 accounts)
- Was your data in the Cutout.Pro breach? (2024, ~19,972,829 accounts)
- Was your data in the Stealer Logs, Jan 2025 breach? (2025, ~71,039,833 accounts)