[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$f375eslqvf8owz":3},{"success":4,"breach":5},true,{"_id":6,"name":7,"title":8,"slug":7,"domain":9,"breachDate":10,"addedDate":11,"publishedAt":12,"modifiedDate":13,"contentUpdatedAt":13,"source":14,"sourceUrl":15,"sourceUrls":16,"pwnCount":12,"affectedCount":12,"affectedCountStatus":20,"affectedCountLowerBound":12,"affectedCountUnit":21,"hasEnglishDescription":4,"contentLocale":22,"availableLocales":23,"translations":25,"severity":28,"dataClasses":29,"description":37,"seoTitle":8,"seoDescription":38,"logoUrl":39,"isVerified":4,"isSensitive":40,"isSpamList":40,"isMalware":40,"company":41},"6a4577ba809ae74a7ace5f47","dayz-forum","DayZ Forum 2016 Data Breach","forums.dayzgame.com","2016-02-01T00:00:00.000Z","2026-07-01T20:25:29.973Z",null,"2026-08-15T14:20:05.822Z","Bohemia Interactive statement reproduced by contemporaneous reporting, historic official forum identity, independent catalog metadata, and sealed exact source evidence","https:\u002F\u002Fhardcoregamer.com\u002Fnews\u002Fdayz-forums-hacked-compromising-user-data-and-passwords\u002F191642\u002F",[15,17,18,19],"https:\u002F\u002Fbreachera.com\u002F","https:\u002F\u002Fweb.archive.org\u002Fweb\u002F20150310153112\u002Fhttp:\u002F\u002Fforums.dayzgame.com\u002F","https:\u002F\u002Fwww.bohemia.net\u002Fgames\u002Fdayz","unknown","people","en",[22,24],"tr",{"en":26,"tr":27},{"slug":7},{"slug":7},"Unknown",[30,31,32,33,34,35,36],"Email addresses","Usernames","IP addresses","Geographic locations","Dates of birth","Passwords","Password salts","\u003Cp>The DayZ Forum 2016 data breach is a verified incident affecting forums.dayzgame.com, operated by Bohemia Interactive. The company statement published in February 2016 says that all forum usernames, e-mail addresses, and passwords were accessed and downloaded by attackers. It also says passwords were not stored in plaintext, but does not disclose an exact affected-person count.\u003C\u002Fp>\u003Ch2>How was the source bound to the event?\u003C\u002Fh2>\u003Cp>The main member in the sealed archive is named DayZ.com_Forum.txt. Its header contains name, e-mail, IP-address, country, birth-date components, password-hash, and salt fields. An independent catalog lists DayZ, 2016, dayz.com, 206,537 records, and the same unusual class combination. The 47-row difference from the complete local file’s 206,584 data rows, together with the filename and schema alignment, binds this exact archive to the event with high confidence; no public count was used as an extraction target.\u003C\u002Fp>\u003Ch2>What appears in LeakData search?\u003C\u002Fh2>\u003Cp>Only the logical field identified as e-mail by the source header is made searchable. When a colon inside a username shifts the physical columns, the row is repaired deterministically by the valid IPv4 and two-letter country code immediately following the e-mail. Two independently compiled parsers processed all 206,584 rows and agreed byte-for-byte on 206,522 accepted e-mail occurrences and 206,479 unique canonical addresses. Usernames, IP addresses, birth dates, password hashes, and salts are not added to search.\u003C\u002Fp>\u003Ch2>How many people were affected?\u003C\u002Fh2>\u003Cp>The operator statement says all forum users were affected but does not give a user count. The 206,537 secondary-catalog records, 206,584 source rows, 206,522 accepted e-mail occurrences, and 206,479 unique canonical addresses use different measurement grains. LeakData does not substitute any of them for a person count and leaves pwnCount unknown.\u003C\u002Fp>\u003Ch2>What does a match mean?\u003C\u002Fh2>\u003Cp>A positive result means the searched address appears in the e-mail field of the sealed source bound to the February 2016 DayZ forum incident. It does not prove that the person’s game account, Steam account, in-game inventory, or payment data was exposed; the incident concerned the forum service. It also does not establish current account ownership or that the address remains active.\u003C\u002Fp>\u003Ch2>What should users do?\u003C\u002Fh2>\u003Cp>If the DayZ forum password was reused on another service, replace it there with a unique password and enable multi-factor authentication where available. Verify the sender and destination domain before opening links in unexpected DayZ or Bohemia messages. A bare e-mail match does not by itself justify assuming another account was compromised or rotating unrelated passwords.\u003C\u002Fp>","Review the verified 2016 DayZ forum incident, its email-only search scope, source binding, and affected-count limits.","\u002Fuploads\u002Flogo\u002Fdayz-forum.png",false,{"name":42,"sector":43,"country":44,"website":45,"websiteArchiveUrl":46,"websiteStatus":46,"websiteCheckedAt":12},"DayZ","Gaming Forum","Czech Republic","dayz.com",""]