Was your data in the Wakanim breach?
Check whether your email address was in it
Check my exposureFree. No password — we email you a six-digit code. This breach and every other one your address appears in.
Wakanim (wakanim.tv) suffered a data breach in 2022 that exposed around 6,706,951 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 August 2022, the European streaming service Wakanim suffered a data breach which was subsequently advertised and sold on a popular hacking forum. The breach exposed 6.7M customer records including email, IP and physical addresses, names and usernames.
Breach record from Have I Been Pwned, CC BY 4.0. 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 Wakanim breach exposed and what each item actually enables:
Also listed in this breach: Browser user agent details, Email addresses, IP addresses, Names, Physical addresses, Usernames.
What to do if you were affected
These steps are ordered for this specific breach — the most urgent action given what leaked comes first.
- Home addresses
Get your address removed from data brokers — they re-list roughly every four months, so this needs repeating. - Names and usernames
Search your usual username to see what else it exposes, and use distinct handles for sensitive accounts. - Email addresses
Treat any message referencing this service with suspicion, and never act on links in unexpected emails. - IP addresses
No direct action needed, but be wary of anyone quoting your location as “proof” of identity. - Confirm you were actually in it
Run a free scan before you spend time on the steps above.
This breach put your details on data-broker sites
Because Wakanim exposed home addresses, this is one of the breaches that feeds people-search and data-broker sites. Those sites scrape leaked databases, combine them with public records, and republish the result as a searchable profile — which is how a single breach turns into a permanent public listing. Removal works, but brokers typically re-list within about four months, so it has to be repeated.
See our broker-by-broker removal guides →
How urgent is this now?
This data has been circulating for around 4 years, which means it has been copied, combined with other leaks and indexed by search tools many times over.
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 Wakanim breach?
The Wakanim breach exposed home addresses, names and usernames, email addresses, ip addresses. Home addresses feed people-search and data-broker sites, which republish them publicly. They also make phishing far more convincing and, in the worst cases, enable real-world harassment.
How many people were affected by the Wakanim breach?
Around 6,706,951 accounts were exposed, making it a large breach.
What should I do if I had a Wakanim account?
Get your address removed from data brokers — they re-list roughly every four months, so this needs repeating. 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 Wakanim breach affected you, these breaches exposed comparable information — worth checking too, since leaked datasets are routinely combined.