Data breaches → EyeEm
Was your data in the EyeEm breach?
2018 · eyeem.com · ~19,611,022 accounts exposedCritical severity · 10/10
EyeEm (eyeem.com) suffered a data breach in 2018 that exposed around 19,611,022 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 2018, photography website EyeEm suffered a data breach. The breach was identified among a collection of other large incidents and exposed almost 20M unique email addresses, names, usernames, bios and password 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 EyeEm breach exposed and what each item actually enables:
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.
Also listed in this breach: Bios, Email addresses, Names, Passwords, 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.
- 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 over 8 years old. Old credentials still cause harm — leaked passwords from a decade ago are still tried against new accounts every day.
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 EyeEm breach?
The EyeEm breach exposed passwords, names and usernames, email 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 EyeEm breach?
Around 19,611,022 accounts were exposed, making it a very large breach by any measure.
What should I do if I had a EyeEm 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 EyeEm breach affected you, these breaches exposed comparable information — worth checking too, since leaked datasets are routinely combined.
- Was your data in the Wattpad breach? (2020, ~268,765,495 accounts)
- Was your data in the SitePoint breach? (2020, ~1,021,790 accounts)
- Was your data in the Tout breach? (2014, ~652,683 accounts)
- Was your data in the 500px breach? (2018, ~14,867,999 accounts)
- Was your data in the Poshmark breach? (2018, ~36,395,491 accounts)
- Was your data in the Chegg breach? (2018, ~39,721,127 accounts)