LiveBreach Intelligence: data breaches, leaks & ransomware, tracked as they surfaceOngoing protection: GalaxyWarden →
Recent BreachesData breach tracker

Recent Breaches › EyeEm Data Breach (2018)

CRITICAL severityConfirmedHow we verify

EyeEm Data Breach (2018): What Was Exposed & What To Do

RBRecent Breaches Breach Intelligence·February 28, 2018
EyeEm Data Breach (2018)

Reported February 28, 2018. Approximately 19.6M people affected.

CRITICAL
Severity
19.6M
People affected
5
Data types exposed
February 28, 2018
Disclosed
ShareXLinkedInFacebookRedditWhatsAppTelegram

The EyeEm Data Breach (2018) (reported February 28, 2018) exposed Bios, Email addresses, Names and Passwords belonging to roughly 19.6M people. If you have an account with them, your information may now be circulating on the open web and with data brokers. Here’s exactly what happened, how to check if you were affected, and what to do next.

Severity & verification
CRITICAL severityConfirmed
Account credentials exposed.
Corroborated by an official disclosure or a verified breach feed.
Was your email in the EyeEm Data Breach (2018) breach?
19.6M accounts were exposed here. See if yours is one — and every other breach it’s in. 15-sec check, no card.

By running your scan you agree to the Terms and Conditions and the Privacy Policy, and to GalaxyWarden emailing you the results of this scan.

People whose email addresses, names, and login details were stored by EyeEm now face the possibility that those details have circulated beyond the company’s control. When such information appears in large collections of breach data, it can be used for targeted phishing, credential-stuffing attacks against other services, or unwanted profiling. The incident was first noted publicly on 28 February 2018. It involved the photography platform EyeEm and exposed records belonging to 19.6 million individuals. The data included email addresses, names, usernames, biographical text, and password hashes. The breach was identified as part of a larger set of incidents rather than through a direct disclosure by the company at the time.

What happened

In February 2018 EyeEm, a photography website, experienced a data breach. The event was detected among a group of other large incidents and involved the exposure of nearly 20 million unique email addresses along with associated names, usernames, biographical information, and password hashes. No further technical details about the method of access or the exact timing of the intrusion have been made public.

How a breach like this happens

Incidents affecting online platforms commonly begin with the compromise of a web application, server, or third-party integration that stores user records. Attackers may exploit unpatched software, weak authentication controls, or stolen administrative credentials to reach databases containing account information. Once inside, they can copy files containing email addresses, names, and hashed passwords. The stolen material is sometimes later found in aggregated collections of breach data rather than being announced by the affected organisation.

Who is EyeEm?

EyeEm operates an online service that allows users to upload, share, and license photographs. Like other platforms in the photography and social-media sector, it maintains accounts that link personal identifiers with login credentials. A breach at such a service is consequential because the data it holds can be reused across many other websites where individuals employ the same email address or password.

What data was at risk

The records reported as exposed contained email addresses, names, usernames, biographical text, and password hashes. Organisations of this type routinely store additional profile details and image metadata, yet the precise scope of every field accessed in this case remains unconfirmed beyond the categories already listed.

Why it matters

Email addresses combined with password hashes can be tested against other online services, increasing the chance that accounts belonging to the same individuals will be accessed without their knowledge. Names and biographical information add context that can support more convincing social-engineering attempts. For the organisation, the event highlights the long-term costs of storing user credentials and the difficulty of containing data once it has left its original environment.

If your data was in this breach

Begin by changing the password on your EyeEm account and on any other service where the same password or a close variation was used. Enable multi-factor authentication wherever it is offered. You can run a free exposure scan of your email address against known breach data to check whether your information appears in additional incidents.

AICompiled with AI assistance from public sources and published under our editorial standards.

Editorial & sourcing policy
Recent Breaches is a breach-monitoring service and news aggregator. We do not exfiltrate, host, purchase, or redistribute stolen data, and we do not hold the data claimed in leak-site listings. Incidents are compiled from publicly accessible sources and threat-intelligence platforms and are reported as claims attributed to their source. We promptly correct or remove material shown to be inaccurate — write to support@galaxywarden.com or press@recentbreaches.com.
Check if you’re exposed →

How this breach connects

Company

Method

SourceBreach data provided in part by Have I Been Pwned, used under CC BY 4.0.

CompanyEyeEm security record
73/100
DoxxScan™ · Moderate doxx risk
C- 64Below-average record

1 reported incident on record.

See EyeEm’s full breach history →

More recent breaches

IIMJobs Data Breach (2018)December 31, 2018BannerBit Data Breach (2018)December 29, 2018BlankMediaGames Data Breach (2018)December 28, 2018OGUsers (2019 breach) Data Breach (2018)December 26, 2018

Latest breaches

Read GalaxyWarden’s full analysis of the EyeEm Data Breach (2018) →

Verified breach. Breach data provided in part by Have I Been Pwned, used under CC BY 4.0.

Breach listings — particularly those originating from ransomware or leak sites — are third-party claims that may be unverified, incomplete, or inaccurate. A listing does not by itself confirm that a breach occurred or that any specific data was exposed. Severity is an automated assessment, not a definitive rating. Verification status is shown where available.

Attributions to threat groups and methods reflect public reporting and, in some cases, unverified claims made by the groups themselves; they may be incomplete or later revised. Recent Breaches and GalaxyWarden are independent and are not affiliated with, and do not endorse, any company or group named on this page. This information is aggregated from public sources for awareness only and is not legal, security, or investment advice.

ShareXLinkedInFacebookRedditWhatsAppTelegram