Evony Data Breach (2016): What Was Exposed & What To Do
SourceBreach data provided in part by Have I Been Pwned, used under CC BY 4.0.
The Evony Data Breach (2016) (reported June 1, 2016) exposed Email addresses, IP addresses, Passwords and Usernames belonging to roughly 29.4M 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.
Breaking down the breach
Contemporary accounts state that the Evony service was accessed without authorization, leading to the extraction of account records. The reported dataset contained 29.4 million unique entries. The exposed fields were limited to usernames, email addresses, IP addresses, and MD5 hashes of passwords stored without additional salting. No further technical details about the intrusion method, duration, or subsequent actions by the operators have been made public in the available records.
How a breach like this happens
Incidents involving online services often begin with the exploitation of application vulnerabilities, weak authentication controls, or compromised administrative credentials. Once inside the environment, an actor can query databases that store user account information. In older systems, password data was sometimes stored using unsalted cryptographic hashes such as MD5, which reduces the computational effort required to recover plaintext values if the hashes are later obtained. After extraction, the material may be shared or sold on forums that traffic in stolen records.
Who is Evony?
Evony operates an online multiplayer strategy game that requires users to create accounts for play. Like other services in the gaming sector, it collects identifiers and contact details to manage accounts, enforce rules, and communicate with players. A compromise at a platform of this type is consequential because the data can be combined with records from other breaches to build more complete profiles of individuals who maintain accounts across multiple sites.
What was likely exposed
The documented records list four categories of information: usernames, email addresses, IP addresses, and MD5 password hashes without salt. No additional data types, such as payment details or full names, are identified in the available reporting. Organizations that operate free-to-play games commonly store only the minimal fields needed for account creation and login; however, the precise contents of the Evony dataset remain limited to the four fields noted above.
What's at stake
Individuals whose records appeared in the dataset face an elevated risk that their email addresses and password hashes could be tested against other services. Because the hashes lack salt, automated tools can attempt to recover matching passwords more efficiently than with modern storage methods. For the organization, the incident highlights the long-term retention of legacy authentication data and the potential for reputational and operational costs when older records become public.
Were you affected?
Anyone who created an Evony account before mid-2016 can treat their email address and any reused password as potentially known to third parties. The immediate practical step is to change the password on the Evony account and on any other service that uses the same credentials. Users can also run a free exposure scan of their email address against known breach datasets to determine whether their information appears in additional incidents.
AICompiled with AI assistance from public sources and published under our editorial standards.
How this breach connects
More recent breaches
Anti Public Combo List Data Breach (2016)Ethereum Data Breach (2016)PayAsUGym Data Breach (2016)MrExcel Data Breach (2016)Latest breaches
Read GalaxyWarden’s full analysis of the Evony Data Breach (2016) →
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.