Mappery Data Breach (2018): What Was Exposed & What To Do
SourceBreach data provided in part by Have I Been Pwned, used under CC BY 4.0.
The Mappery Data Breach (2018) (reported December 11, 2018) exposed Email addresses, Geographic locations, Passwords and Usernames belonging to roughly 205K 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.
What happened
The breach affected 205,000 unique email addresses along with associated usernames, geographic locations, and passwords. The passwords were stored in unsalted SHA-1 format. Public records indicate the incident was identified and reported in December 2018. No information has been released about how the data were obtained or whether the exposure was limited to a single dataset or extended over time.
How a breach like this happens
Incidents involving the exposure of user credentials and location data often result from unauthorized access to application databases or backup files. Attackers may exploit unpatched software, weak authentication controls, or misconfigured storage systems to retrieve records in bulk. Once obtained, the data can be copied and later circulated without the knowledge of the affected organization. The use of unsalted SHA-1 hashing, a method known to be computationally feasible to reverse under certain conditions, increases the potential usability of any passwords that were captured.
Who is Mappery?
Mappery operated as a website focused on maps and geographic information contributed or viewed by its users. Organizations of this type typically maintain accounts that link email addresses and usernames to location-based content. A breach at such a service is consequential because the data can reveal patterns of user movement or interests tied to specific places, in addition to the more common exposure of login credentials.
What was likely exposed
The reported incident included email addresses, usernames, geographic locations, and passwords stored as unsalted SHA-1 hashes. These data types were explicitly named in connection with the 205,000 affected accounts. No additional categories of information, such as full names, payment details, or private messages, have been confirmed as part of the exposure. The exact contents of any individual record remain unverified beyond the categories listed at the time of reporting.
The real-world impact
Individuals whose information appeared in the dataset face the possibility that their email addresses and usernames could be used for targeted phishing or account enumeration on other services. Geographic locations tied to accounts may disclose habitual travel or areas of interest. Passwords stored as unsalted SHA-1 hashes could be subjected to offline cracking attempts, raising the risk of credential reuse on unrelated sites. For the organization, the incident represents a loss of user trust and potential regulatory scrutiny, though the scale of any follow-on effects has not been quantified.
What to do if you're exposed
Anyone who used Mappery should change the password associated with that account and any other service where the same password was reused. Enable multi-factor authentication on accounts that support it, and monitor email for unusual login attempts or unsolicited messages. A free exposure scan of an email address against known breach datasets can indicate whether the address has appeared in this or other incidents.
AICompiled with AI assistance from public sources and published under our editorial standards.
How this breach connects
More recent breaches
IIMJobs Data Breach (2018)BannerBit Data Breach (2018)BlankMediaGames Data Breach (2018)Roll20 Data Breach (2018)Latest breaches
Read GalaxyWarden’s full analysis of the Mappery 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.