InnoGames Attributed 2016 Dataset
The dataset attributed to InnoGames in June 2016 is listed by a third-party catalogue with a scope value of 657,908 and email, IP-address, username, password, and password-salt fields.
Exposed Data Types
1- Email addresses
About This Record
Manual review found no company notice, reliable independent report, or verified breach-index entry authenticating the event identity, date, count, or field list. The 657,908 value is therefore not displayed as an affected-user or verified-record count.
Production evidence is narrower but measurable. An email-only job named innogames.txt processed 600,084 lines and produced 600,039 unique email addresses in the live index. The job processed no usernames, passwords, IP addresses, or other sensitive fields. The local file name and its association with this record do not by themselves authenticate the file's original source, its attribution to InnoGames, the June 2016 date, or the third party's 657,908 value.
Which fields are evidenced?
Only email addresses are evidenced in the local dataset. IP addresses, usernames, passwords, and password salts are retained as unsupported third-party claims; an MD5 method also cannot be established without a sample, schema, or technical report. The 600,084 processed lines, 600,039 unique emails, and 657,908 external claim are different measures and are not combined. A local match does not establish an InnoGames account, game use, username, password, payment data, or account takeover.
Safe steps and the condition for re-review
If a person independently knows that they used InnoGames in 2016 and knows which password was used for that account, only a reused old password should be replaced with a unique password, and multifactor authentication should be enabled on the associated email account. A password, gaming activity, or identity must not be inferred from an email match alone. If a company notice, original file listing and hashes, sample schema, or reliable independent verification emerges, the attribution, date, count unit, and alleged fields can be reviewed again.
Verification and editorial method
LeakData compares the incident name, date, affected-record count, and exposed data types with accessible sources. Unverified fields are not presented as facts, and records are updated when new evidence becomes available.
Report missing or incorrect information
