Was your data in the Liker 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.
Liker (liker.com) suffered a data breach in 2021 that exposed around 465,141 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 March 2021, the self-proclaimed "kinder, smarter social network" Liker suffered a data breach, allegedly in retaliation for the Gab data breach and scraping of data from Parler. The site remained offline after the breach which exposed 465k email addresses in addition to names, dates of birth, education levels, private messages, security questions and answers in plain text, passwords stored as bcrypt hashes and other personal data attributes. Liker did not respond when contacted about the breach.
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 Liker breach exposed and what each item actually enables:
Also listed in this breach: Auth tokens, Dates of birth, Education levels, Email addresses, Geographic locations, IP addresses, Names, Passwords, Phone numbers, Private messages, Security questions and answers, Social media profiles, 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.
- Passwords
Change this password everywhere you have reused it, starting with your email account — whoever controls your email can reset everything else. - Private messages
Consider what was discussed on this service and whether anything needs changing (shared passwords, personal disclosures). - Security questions and answers
Change the answers on every account using them, and treat the answers as passwords (random strings stored in a password manager). - 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.
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 Liker breach?
The Liker breach exposed passwords, private messages, security questions and answers, dates of birth, phone numbers, location data, names and usernames, email addresses, ip 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 Liker breach?
Around 465,141 accounts were exposed, making it a mid-sized breach.
What should I do if I had a Liker 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 Liker breach affected you, these breaches exposed comparable information — worth checking too, since leaked datasets are routinely combined.