[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$f3pd86z0q8cm4k":3,"$fqgzcro5jnkk3":58},{"success":4,"breach":5},true,{"_id":6,"name":7,"title":8,"slug":9,"domain":10,"breachDate":11,"addedDate":12,"publishedAt":13,"modifiedDate":14,"contentUpdatedAt":14,"source":15,"sourceUrl":16,"sourceUrls":17,"pwnCount":19,"affectedCount":19,"affectedCountStatus":20,"affectedCountLowerBound":13,"affectedCountUnit":21,"hasEnglishDescription":4,"contentLocale":22,"availableLocales":23,"translations":33,"severity":44,"dataClasses":45,"description":49,"seoTitle":50,"seoDescription":51,"logoUrl":52,"isVerified":53,"isSensitive":53,"isSpamList":53,"isMalware":53,"company":54},"6aae23ea5048d9bd35b74025","Kaixin001 2011","Kaixin001 Alleged Data Exposure","kaixin001-2011","kaixin001.com","2011-12-25T00:00:00.000Z","2026-09-19T05:55:53.945Z",null,"2026-10-10T08:26:39.870Z","Kaixin001 Chinese social network plaintext database leak","http:\u002F\u002Fwww.kaixin001.com\u002F",[16,18],"https:\u002F\u002Fen.wikipedia.org\u002Fwiki\u002FKaixin001",5482302,"known","email_identifiers","en",[22,24,25,26,27,28,29,30,31,32],"tr","zh","hi","es","ar","fr","bn","pt","ru",{"en":34,"tr":35,"zh":36,"hi":37,"es":38,"ar":39,"fr":40,"bn":41,"pt":42,"ru":43},{"slug":9},{"slug":9},{"slug":9},{"slug":9},{"slug":9},{"slug":9},{"slug":9},{"slug":9},{"slug":9},{"slug":9},"Critical",[46,47,48],"Email addresses","Passwords","Usernames","\u003Cp>\u003Cstrong>The 2011 Kaixin001 (开心网) data breach\u003C\u002Fstrong> occurred in December 2011 when user databases belonging to \u003Cstrong>Kaixin001\u003C\u002Fstrong> (\u003Ccode>kaixin001.com\u003C\u002Fcode>), a leading Chinese social networking platform launched in 2008, were leaked online as part of the nationwide credential exposure wave affecting major contemporary Chinese web services.\u003C\u002Fp>\u003Ch2>What information was compromised in the Kaixin001 incident?\u003C\u002Fh2>\u003Cp>The leaked text database files comprise 8,288,756 user credential lines. Compromised data classes include:\u003C\u002Fp>\u003Cul>\u003Cli>\u003Cstrong>User Identifiers:\u003C\u002Fstrong> Internal user account sequence numbers and display handles.\u003C\u002Fli>\u003Cli>\u003Cstrong>Contact Credentials:\u003C\u002Fstrong> Primary email addresses (predominantly \u003Ccode>@qq.com\u003C\u002Fcode>, \u003Ccode>@126.com\u003C\u002Fcode>, \u003Ccode>@163.com\u003C\u002Fcode>, and \u003Ccode>@sina.com\u003C\u002Fcode>).\u003C\u002Fli>\u003Cli>\u003Cstrong>Authentication Secrets:\u003C\u002Fstrong> User account passwords stored in unencrypted \u003Cstrong>plaintext\u003C\u002Fstrong>.\u003C\u002Fli>\u003C\u002Ful>\u003Ch2>How many accounts were affected?\u003C\u002Fh2>\u003Cp>Standardized RFC 5322 ASCII canonical verification confirmed \u003Cstrong>5,482,302 unique valid email addresses\u003C\u002Fstrong> across 8,288,756 records.\u003C\u002Fp>\u003Ch2>Security advisory & credential precautions\u003C\u002Fh2>\u003Cp>Cleartext password exposure permits immediate credential stuffing attacks against linked email and modern online accounts. Impacted users should:\u003C\u002Fp>\u003Cul>\u003Cli>Immediately update passwords on any service where the same login credentials were utilized.\u003C\u002Fli>\u003Cli>Adopt a password manager and enable multi-factor authentication (MFA) across critical portals.\u003C\u002Fli>\u003C\u002Ful>","Kaixin001 Alleged Data Exposure (5.5 Million Email Identifiers)","Kaixin001 Alleged Data Exposure. 5.5 million email identifiers are reported. Reported data: Email addresses, Passwords, Usernames. Review the scope, risks…","\u002Fuploads\u002Flogo\u002Fkaixin001.webp",false,{"name":55,"sector":56,"country":57,"website":57,"websiteArchiveUrl":57,"websiteStatus":57,"websiteCheckedAt":13},"Kaixin001","Social Media","",{"success":4,"breaches":59},[60,67,74,81],{"slug":61,"title":62,"companyName":63,"logoUrl":64,"breachDate":65,"affectedCount":66,"affectedCountStatus":20},"meta-instagram-hts-2026","Meta Instagram HTS 2026 Data Breach","Meta Platforms, Inc.","\u002Fuploads\u002Flogo\u002Fmeta_com.svg","2026-04-17T00:00:00.000Z",20225,{"slug":68,"title":69,"companyName":70,"logoUrl":71,"breachDate":72,"affectedCount":73,"affectedCountStatus":20},"instagram","Instagram 2026 Data Breach Claim","Instagram","\u002Fuploads\u002Flogo\u002Finstagram_com.webp","2026-01-07T00:00:00.000Z",6215150,{"slug":75,"title":76,"companyName":77,"logoUrl":78,"breachDate":79,"affectedCount":80,"affectedCountStatus":20},"discord-5ca-2025","Discord Data Breach","Discord Inc.","\u002Fuploads\u002Flogo\u002Fdiscord.svg","2025-09-20T00:00:00.000Z",74729,{"slug":82,"title":83,"companyName":84,"logoUrl":85,"breachDate":86,"affectedCount":87,"affectedCountStatus":20},"spoutible","Spoutible Data Breach","Spoutible","\u002Fuploads\u002Flogo\u002Fspoutible_com.webp","2024-01-31T00:00:00.000Z",207114]