[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$f1053qyv7j34de":3},{"success":4,"breach":5},true,{"_id":6,"name":7,"title":8,"slug":7,"domain":9,"breachDate":10,"addedDate":11,"modifiedDate":12,"contentUpdatedAt":12,"source":13,"sourceUrl":14,"sourceUrls":15,"pwnCount":17,"affectedCount":17,"affectedCountStatus":18,"affectedCountLowerBound":19,"affectedCountUnit":20,"hasEnglishDescription":4,"severity":21,"dataClasses":22,"description":26,"seoTitle":27,"seoTitleEn":28,"seoDescription":27,"seoDescriptionEn":29,"logoUrl":30,"isVerified":4,"isSensitive":4,"isSpamList":31,"isMalware":31,"company":32},"68e3266eda11adda48825104","battlefy","Battlefy January 2016 Credential Incident","battlefy.com","2016-01-11T00:00:00.000Z","2022-07-29T00:24:33.000Z","2026-07-29T11:13:00.741Z","Authenticated Battlefy credential corpus and company statement","https:\u002F\u002Fwww.reddit.com\u002Fr\u002Fesports\u002Fcomments\u002F40igd4\u002Fhackers_hit_esports_site_battlefy_and_release\u002F",[14,16],"https:\u002F\u002Fbattlefy.com\u002Fterms-of-service",83610,"known",null,"records","Medium",[23,24,25],"Email addresses","Usernames","Bcrypt password hashes","\u003Cp>\u003Cstrong>The January 2016 Battlefy credential incident\u003C\u002Fstrong> consists of emails, usernames, and bcrypt password hashes. The external source reports 83,610 accounts and local search contains 89,276 records; the local measure is 5,666 higher. January 11 is the structured incident or catalogue date.\u003C\u002Fp>\u003Cp>Bcrypt is not plaintext and slows offline password testing, but algorithm cost, field prevalence, whether any particular hash was cracked, password currentness, and reuse are unknown at person level. Names, phones, physical addresses, government IDs, payments, tournament results, prizes, team roles, and administrator privileges are not classes.\u003C\u002Fp>\u003Cp>A match can establish only that an email occurs in the local subset associated with Battlefy. It does not establish identity, an active account, a player, team, or organizer role, tournament participation, username or password ownership, field co-occurrence, account takeover, or misuse. If the old password genuinely belonged to the person and was reused, it should be replaced.\u003C\u002Fp>","","Battlefy January 2016 Credential Incident (83.6 Thousand Records)","Battlefy January 2016 Credential Incident. 83.6 Thousand records were reported. Reported data: Email addresses, Usernames, Bcrypt password hashes. Review the…","\u002Fuploads\u002Flogo\u002Fbattlefy_com.webp",false,{"name":33,"sector":34,"country":35,"website":9,"websiteArchiveUrl":27,"websiteStatus":27,"websiteCheckedAt":19},"Battlefy","Esports tournament platform","Canada"]