Data breaches → Ualabee
Was your data in the Ualabee breach?
2025 · ualabee.com · ~472,296 accounts exposedHigh severity · 7/10
Ualabee (ualabee.com) suffered a data breach in 2025 that exposed around 472,296 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, the South American mobility services platform Ualabee had hundreds of thousands of records scraped from an interface on their platform. The data included 472k unique email addresses along with names, profile photos, dates of birth and phone numbers.
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 Ualabee breach exposed and what each item actually enables:
Date of birth is a permanent identifier used to verify identity by phone. Combined with a name and address it is often enough to impersonate you.
Enables SIM-swap attacks (hijacking your number to intercept SMS codes), smishing, and voice scams that appear to come from your bank.
Links this leak to your other accounts — a reused username lets anyone build a profile of you across platforms.
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.
Also listed in this breach: Dates of birth, Email addresses, Names, Phone numbers, Profile photos.
What to do if you were affected
These steps are ordered for this specific breach — the most urgent action given what leaked comes first.
- 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.
- 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.
- 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.
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 Ualabee breach?
The Ualabee breach exposed dates of birth, phone numbers, names and usernames, email addresses. Date of birth is a permanent identifier used to verify identity by phone. Combined with a name and address it is often enough to impersonate you.
How many people were affected by the Ualabee breach?
Around 472,296 accounts were exposed, making it a mid-sized breach.
What should I do if I had a Ualabee account?
Never confirm your date of birth to an inbound caller — hang up and dial the organisation back on a published number. 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 Ualabee breach affected you, these breaches exposed comparable information — worth checking too, since leaked datasets are routinely combined.
- Was your data in the Salvadoran Citizens breach? (2024, ~946,989 accounts)
- Was your data in the Paidwork breach? (2026, ~23,272,765 accounts)
- Was your data in the CyberServe breach? (2021, ~1,107,034 accounts)
- Was your data in the Ajarn breach? (2018, ~266,399 accounts)
- Was your data in the Wishbone (2020) breach? (2020, ~9,705,172 accounts)
- Was your data in the Miljödata breach? (2025, ~870,108 accounts)