Was your data in the Odido 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.
Odido (odido.nl) suffered a data breach in 2026 that exposed around 6,077,025 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 February 2026, Dutch telco Odido was the victim of a data breach and subsequent extortion attempt. Shortly after, a total of 6M unique email addresses were published across four separate data releases over consecutive days. The exposed data includes names, physical addresses, phone numbers, bank account numbers, dates of birth, customer service notes and passport, driver’s licence and European national ID numbers. Odido has published a disclosure notice including an FAQ to support affected customers.
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 Odido breach exposed and what each item actually enables:
Also listed in this breach: Bank account numbers, Customer service records, Dates of birth, Driver's licenses, Email addresses, Genders, Government issued IDs, Names, Passport numbers, Phone numbers, Physical addresses.
What to do if you were affected
These steps are ordered for this specific breach — the most urgent action given what leaked comes first.
- Payment or bank details
Contact your bank, ask them to monitor or reissue the card, and check statements for small “test” transactions. - Government identifiers
Consider a credit freeze or fraud alert with the credit reference agencies, and watch for accounts you did not open. - Home addresses
Get your address removed from data brokers — they re-list roughly every four months, so this needs repeating. - Dates of birth
Never confirm your date of birth to an inbound caller — hang up and dial the organisation back on a published number. - Phone numbers
Move two-factor authentication off SMS to an authenticator app or passkey, and add a port-out PIN with your mobile provider. - 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 Odido 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 breach is recent, so the data is actively traded and the risk is at its highest right now.
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 Odido breach?
The Odido breach exposed payment or bank details, government identifiers, home addresses, dates of birth, phone numbers, names and usernames, email addresses. Direct financial fraud, plus convincing scam calls that quote your real card or account details to establish trust.
How many people were affected by the Odido breach?
Around 6,077,025 accounts were exposed, making it a large breach.
What should I do if I had a Odido account?
Contact your bank, ask them to monitor or reissue the card, and check statements for small “test” transactions. 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 Odido breach affected you, these breaches exposed comparable information — worth checking too, since leaked datasets are routinely combined.