Data breaches → CityBee
Was your data in the CityBee breach?
2021 · citybee.lt · ~110,156 accounts exposedCritical severity · 10/10
CityBee (citybee.lt) suffered a data breach in 2021 that exposed around 110,156 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 2021, the Lithuanian car-sharing service CityBee announced they'd suffered a data breach that exposed 110k customers' personal information. The breach exposed names, email addresses, government issued IDs and passwords stored as unsalted SHA-1 hashes.
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 CityBee breach exposed and what each item actually enables:
The strongest identity-theft material there is — enough to open credit accounts or file fraudulent claims in your name.
Attackers replay leaked passwords across other sites (“credential stuffing”). Because most people reuse passwords, one leak often unlocks email, shopping and banking accounts elsewhere.
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.
What to do if you were affected
These steps are ordered for this specific breach — the most urgent action given what leaked comes first.
- Government identifiers: Consider a credit freeze or fraud alert with the credit reference agencies, and watch for accounts you did not open.
- Passwords: Change this password everywhere you have reused it, starting with your email account — whoever controls your email can reset everything else.
- 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 data has been circulating for around 5 years, which means it has been copied, combined with other leaks and indexed by search tools many times over.
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 CityBee breach?
The CityBee breach exposed government identifiers, passwords, names and usernames, email addresses. The strongest identity-theft material there is — enough to open credit accounts or file fraudulent claims in your name.
How many people were affected by the CityBee breach?
Around 110,156 accounts were exposed, making it a mid-sized breach.
What should I do if I had a CityBee account?
Consider a credit freeze or fraud alert with the credit reference agencies, and watch for accounts you did not open. 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 CityBee breach affected you, these breaches exposed comparable information — worth checking too, since leaked datasets are routinely combined.
- Was your data in the RentoMojo breach? (2023, ~2,185,697 accounts)
- Was your data in the ViewFines breach? (2018, ~777,649 accounts)
- Was your data in the eThekwini Municipality breach? (2016, ~81,830 accounts)
- Was your data in the Baydöner breach? (2026, ~1,266,822 accounts)
- Was your data in the Vodafone breach? (2013, ~56,021 accounts)
- Was your data in the Upstox breach? (2021, ~111,002 accounts)