[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$f1owske16lcmo3":3,"$f2gcl52j09w2d6":56},{"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":18,"affectedCount":18,"affectedCountStatus":19,"affectedCountLowerBound":13,"affectedCountUnit":20,"hasEnglishDescription":4,"contentLocale":21,"availableLocales":22,"translations":32,"severity":43,"dataClasses":44,"description":47,"seoTitle":48,"seoDescription":49,"logoUrl":50,"isVerified":4,"isSensitive":51,"isSpamList":51,"isMalware":51,"company":52},"6aae15b08a3061dba817f648","Renren 2011","Renren Data Breach","renren-2011","renren.com","2011-12-21T00:00:00.000Z","2026-09-19T04:55:12.280Z",null,"2026-10-10T00:10:58.251Z","Renren Chinese social networking platform plaintext database breach","https:\u002F\u002Fen.wikipedia.org\u002Fwiki\u002FRenren",[16],4374869,"known","unknown","en",[21,23,24,25,26,27,28,29,30,31],"tr","zh","hi","es","ar","fr","bn","pt","ru",{"en":33,"tr":34,"zh":35,"hi":36,"es":37,"ar":38,"fr":39,"bn":40,"pt":41,"ru":42},{"slug":9},{"slug":9},{"slug":9},{"slug":9},{"slug":9},{"slug":9},{"slug":9},{"slug":9},{"slug":9},{"slug":9},"Critical",[45,46],"Email addresses","Passwords","\u003Cp>\u003Cstrong>The 2011 Renren (人人网) data breach\u003C\u002Fstrong> occurred in December 2011 when \u003Cstrong>Renren\u003C\u002Fstrong> (\u003Ccode>renren.com\u003C\u002Fcode>), historically recognized as China's leading real-name social network (\"the Facebook of China\"), suffered a catastrophic data disclosure that was subsequently acknowledged by the company.\u003C\u002Fp>\u003Ch2>What information was affected in the Renren incident?\u003C\u002Fh2>\u003Cp>The leaked text database export (\u003Ccode>Renren.txt\u003C\u002Fcode>) comprises \u003Cstrong>4,768,600 user accounts\u003C\u002Fstrong>. The compromised data classes include:\u003C\u002Fp>\u003Cul>\u003Cli>\u003Cstrong>Contact Coordinates:\u003C\u002Fstrong> User primary email addresses (predominantly \u003Ccode>@qq.com\u003C\u002Fcode>, \u003Ccode>@126.com\u003C\u002Fcode>, \u003Ccode>@163.com\u003C\u002Fcode>, \u003Ccode>@sina.com\u003C\u002Fcode>, and \u003Ccode>@hotmail.com\u003C\u002Fcode>).\u003C\u002Fli>\u003Cli>\u003Cstrong>Authentication Credentials:\u003C\u002Fstrong> User account passwords stored entirely in \u003Cstrong>plaintext\u003C\u002Fstrong> (unencrypted and unhashed).\u003C\u002Fli>\u003C\u002Ful>\u003Ch2>How many accounts were affected?\u003C\u002Fh2>\u003Cp>Strict RFC 5322 ASCII canonical verification confirmed \u003Cstrong>3,031,620 unique valid email addresses\u003C\u002Fstrong> across the database.\u003C\u002Fp>\u003Ch2>Technical analysis and security risks\u003C\u002Fh2>\u003Cp>The total absence of cryptographic protection meant credentials were immediately usable without cracking. Threat actors weaponized the cleartext credentials in massive credential stuffing campaigns against contemporary Chinese web platforms, email providers, and social portals.\u003C\u002Fp>\u003Ch2>Corporate disclosure & recommended actions\u003C\u002Fh2>\u003Cp>Following the disclosure, Renren officially confirmed the incident, advising its user base to immediately reset their passwords. Affected individuals should:\u003C\u002Fp>\u003Cul>\u003Cli>Immediately update passwords on any email services and external platforms where identical credentials were used.\u003C\u002Fli>\u003Cli>Activate multi-factor authentication (MFA \u002F 2FA) across all active accounts.\u003C\u002Fli>\u003C\u002Ful>","Renren Data Breach (4.4 Million Reported Records)","Renren Data Breach. 4.4 million records are reported. Reported data: Email addresses, Passwords. Review the scope, risks, and protective steps.","\u002Fuploads\u002Flogo\u002Frenren.webp",false,{"name":53,"sector":54,"country":55,"website":55,"websiteArchiveUrl":55,"websiteStatus":55,"websiteCheckedAt":13},"Renren","Social Media","",{"success":4,"breaches":57},[58,65,72,79],{"slug":59,"title":60,"companyName":61,"logoUrl":62,"breachDate":63,"affectedCount":64,"affectedCountStatus":19},"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":66,"title":67,"companyName":68,"logoUrl":69,"breachDate":70,"affectedCount":71,"affectedCountStatus":19},"instagram","Instagram 2026 Data Breach Claim","Instagram","\u002Fuploads\u002Flogo\u002Finstagram_com.webp","2026-01-07T00:00:00.000Z",6215150,{"slug":73,"title":74,"companyName":75,"logoUrl":76,"breachDate":77,"affectedCount":78,"affectedCountStatus":19},"discord-5ca-2025","Discord Data Breach","Discord Inc.","\u002Fuploads\u002Flogo\u002Fdiscord.svg","2025-09-20T00:00:00.000Z",74729,{"slug":80,"title":81,"companyName":82,"logoUrl":83,"breachDate":84,"affectedCount":85,"affectedCountStatus":19},"spoutible","Spoutible Data Breach","Spoutible","\u002Fuploads\u002Flogo\u002Fspoutible_com.webp","2024-01-31T00:00:00.000Z",207114]