[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$fqn5ccsp6c5nd":3},{"success":4,"breach":5},true,{"_id":6,"name":7,"title":8,"slug":9,"domain":10,"breachDate":11,"addedDate":12,"publishedAt":12,"modifiedDate":13,"contentUpdatedAt":14,"source":15,"sourceUrl":16,"sourceUrls":17,"pwnCount":22,"affectedCount":22,"affectedCountStatus":23,"affectedCountLowerBound":24,"affectedCountUnit":25,"hasEnglishDescription":4,"contentLocale":26,"availableLocales":27,"translations":29,"severity":32,"dataClasses":33,"description":44,"seoTitle":45,"seoDescription":46,"logoUrl":47,"isVerified":48,"isSensitive":4,"isSpamList":48,"isMalware":48,"company":49},"370b020db99aa2ff4a9a0da5","GameGrin","GameGrin October 2018 Unverified Data Breach","gamegrin-2018","gamegrin.com","2018-10-01T00:00:00.000Z","2026-08-21T15:18:07.404Z","2026-09-17T19:40:48.451Z","2026-09-17T16:54:14.340Z","Official GameGrin pages, sealed third-party GameGrin archive, and independent public incident metadata","https:\u002F\u002Fwww.gamegrin.com\u002F",[16,18,19,20,21],"https:\u002F\u002Fwww.gamegrin.com\u002Fabout-us\u002Fgamegrin\u002F","https:\u002F\u002Fwww.gamegrin.com\u002Fabout-us\u002Fprivacy\u002F","https:\u002F\u002Fleakedsource.com\u002Fbreaches\u002Fgamegrin-data-breach-ae49d660","https:\u002F\u002Fdata-wells.niamonx.io\u002FBreach\u002FGameGrin",90295,"known",null,"people","en",[26,28],"tr",{"en":30,"tr":31},{"slug":9},{"slug":9},"Medium",[34,35,36,37,38,39,40,41,42,43],"Email addresses","Password hashes","Usernames","IP addresses","Dates of birth","Instant messaging identifiers","Website URLs","Profile data","Reputation data","Forum activity data","\u003Cp>The \u003Cstrong>dataset associated with GameGrin\u003C\u002Fstrong> is based on two MySQL snapshots in a complete, integrity-verified third-party 7z archive. Both SQL members carry archive metadata dated 5 October 2018. Two independent public breach indexes also publish an October 2018 claim for GameGrin at an approximate scale of 90.4 thousand records. These markers are consistent with the sealed source in brand, month, approximate scale, and field classes; however, no operator-published incident confirmation was located, so the record is published as an unverified third-party data-breach claim.\u003C\u002Fp>\u003Cp>The 14,098,046-byte archive passed its integrity test; all three regular members, totalling 88,677,272 bytes, were accounted for and no nested archive was present. The 43,576,501-byte first SQL dump contains 87,941 tuples and the 45,100,330-byte second dump contains 91,368 tuples. The larger snapshot contains 90,424 rows in its \u003Ccode>user\u003C\u002Fcode> table; this is not a people count or an operator-confirmed affected count. The generic BreachForums packaging note contains no email, row schema, or incident date and was not used as a data source.\u003C\u002Fp>\u003Cp>Only \u003Ccode>user.email\u003C\u002Fcode> and \u003Ccode>user.parentemail\u003C\u002Fcode>, explicitly identified by the DDL and \u003Ccode>INSERT\u003C\u002Fcode> column lists, are authorized for email import. Despite containing “email” in its name, \u003Ccode>user.emailstamp\u003C\u002Fcode> is a timestamp and is not authorized. Across both snapshots, 178,304 of 356,718 authorized field cells are \u003Ccode>NULL\u003C\u002Fcode> and 178,414 are populated; 178,210 canonical-valid occurrences were accepted and 204 values were rejected. Two independent compiled parsers agreed exactly on rows, fields, accepted and rejected values, and occurrence sequences for both sources.\u003C\u002Fp>\u003Cp>The snapshots were not added as separate populations: 87,809 unique emails are shared, 3 occur only in the smaller dump, and 2,483 occur only in the larger dump. Their union contains 90,295 unique canonical emails, all of which passed an independent line validator. A total of 2,262 email-shaped occurrences in fields such as usernames, messaging identifiers, home pages, and salts were not authorized merely by their format and were excluded. Password hashes, usernames, IP addresses, dates of birth, messaging identifiers, profile, reputation, and forum-activity data will not be imported.\u003C\u002Fp>\u003Cp>GameGrin’s current official site confirms the organization and the \u003Ccode>gamegrin.com\u003C\u002Fcode> domain; its official privacy page supports the account-registration and email-processing context but provides no incident statement. No matching entry was found in the current public breach source catalogue, and that absence is not treated as disproof. No operator-confirmed affected-person count was located, so no \u003Ccode>pwnCount\u003C\u002Fcode> is published and the 90,424 rows in the larger snapshot were not fitted to the 90,295 unique email relations. An email match alone would not prove that other fields belong to the same person or that GameGrin confirmed the incident.\u003C\u002Fp>","GameGrin October 2018 Unverified Data Breach (90.3 Thousand People Affected)","Review the GameGrin October 2018 unverified breach, sealed SQL archive, and 90,295 source-verified unique email relations.","\u002Fuploads\u002Flogo\u002Fgamegrin_com.png",false,{"name":7,"sector":50,"country":51,"website":16,"websiteArchiveUrl":52,"websiteStatus":53,"websiteCheckedAt":12},"Gaming media","United Kingdom","","active"]