Eskimi Data Breach (2020): What Was Exposed & What To Do
SourceBreach data provided in part by Have I Been Pwned, used under CC BY 4.0.
The Eskimi Data Breach (2020) (reported September 25, 2020) exposed Dates of birth, Email addresses, Genders and Geographic locations belonging to roughly 1.2M 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.
Inside the incident
The breach affected an AdTech platform that processes user information for digital advertising campaigns. Public reporting at the time stated that 26 million records were obtained, containing 1.2 million unique email addresses along with the other fields listed above. No information has been released about the method of intrusion, the date the data were first accessed, or whether the passwords were subsequently cracked. The organisation has not published a detailed timeline or confirmed whether the unsalted MD5 hashes were later reversed.
How a breach like this happens
Incidents involving advertising platforms often begin with the compromise of a web application, an exposed database, or a misconfigured cloud storage bucket. Once initial access is gained, attackers search for tables that store user profiles and authentication data. Passwords kept as unsalted MD5 hashes can be processed offline with widely available tools, increasing the chance that some credentials become usable. The same datasets frequently contain demographic fields that allow records to be matched across other services.
Eskimi and its sector
Eskimi operates in the programmatic advertising sector, where platforms collect and match user attributes to deliver targeted advertisements across websites and mobile applications. Companies in this field routinely hold email addresses, device identifiers, location data and basic demographic details to build audience segments. A breach at such a firm is consequential because the information is already structured for marketing use and can be repurposed for fraud or more precise phishing campaigns.
What was likely exposed
The breach record names the following data types: dates of birth, email addresses, genders, geographic locations, passwords and usernames. The passwords were stored as unsalted MD5 hashes. The exact contents of every record remain unconfirmed beyond these categories, and no additional fields such as full names or financial details have been reported.
What's at stake
For individuals, the combination of email addresses, usernames and demographic information can facilitate account-recovery attacks on other services that reuse the same credentials. Unsalted MD5 hashes are comparatively weak, so some passwords may already have been recovered and circulated. For the organisation, the incident highlights the long-term liability that comes from retaining identifiable user data in advertising systems without stronger protective controls.
Were you affected?
Check whether your email address appears in public breach datasets by running a free exposure scan on a reputable site that aggregates known incidents. If your address is listed, change the password on any account that still uses it, enable multi-factor authentication, and review recent login activity. Organisations that held the data have not published a notification portal, so individual monitoring of personal accounts remains the most direct step.
AICompiled with AI assistance from public sources and published under our editorial standards.
How this breach connects
More recent breaches
MEO Data Breach (2020)NetGalley Data Breach (2020)MMG Fusion Data Breach (2020)DriveSure Data Breach (2020)Latest breaches
Read GalaxyWarden’s full analysis of the Eskimi Data Breach (2020) →
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.