[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$f31lvprp7duvsh":3,"$f201amsch3qz2u":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":20,"affectedCount":20,"affectedCountStatus":21,"affectedCountLowerBound":13,"affectedCountUnit":22,"hasEnglishDescription":4,"contentLocale":23,"availableLocales":24,"translations":34,"severity":45,"dataClasses":46,"description":49,"seoTitle":50,"seoDescription":51,"logoUrl":52,"isVerified":53,"isSensitive":53,"isSpamList":53,"isMalware":53,"company":54},"6aadcb3397106f4349f4af48","Mop.com 2011","Mop.com Alleged Data Exposure","mop-2011","mop.com","2011-12-25T00:00:00.000Z","2026-09-18T23:37:23.426Z",null,"2026-10-10T10:26:26.047Z","Mop.com Chinese BBS community forum database breach","https:\u002F\u002Fweb.archive.org\u002Fweb\u002F20111230000000\u002Fhttp:\u002F\u002Fwww.mop.com\u002F",[16,18,19],"https:\u002F\u002Fen.wikipedia.org\u002Fwiki\u002FMop.com","https:\u002F\u002Fzh.wikipedia.org\u002Fwiki\u002F%E7%8C%AB%E6%89%91",1883074,"known","email_identifiers","en",[23,25,26,27,28,29,30,31,32,33],"tr","zh","hi","es","ar","fr","bn","pt","ru",{"en":35,"tr":36,"zh":37,"hi":38,"es":39,"ar":40,"fr":41,"bn":42,"pt":43,"ru":44},{"slug":9},{"slug":9},{"slug":9},{"slug":9},{"slug":9},{"slug":9},{"slug":9},{"slug":9},{"slug":9},{"slug":9},"Critical",[47,48],"Email addresses","Passwords","\u003Cp>\u003Cstrong>The 2011 Mop.com data breach\u003C\u002Fstrong> occurred in December 2011 when the user database of \u003Cstrong>Mop.com\u003C\u002Fstrong> (\u003Ccode>mop.com\u003C\u002Fcode> \u002F 猫扑网), one of China's earliest and most influential online community and BBS portals founded in 1997, was leaked publicly during the widespread \"2011 China Password Crisis\".\u003C\u002Fp>\u003Ch2>What information was affected in the Mop.com incident?\u003C\u002Fh2>\u003Cp>The leaked export (\u003Ccode>mop.txt\u003C\u002Fcode>) includes authentication credentials for \u003Cstrong>1,883,074 unique user accounts\u003C\u002Fstrong>:\u003C\u002Fp>\u003Cul>\u003Cli>\u003Cstrong>Valid Email Identifiers:\u003C\u002Fstrong> Canonical user email addresses primarily across Chinese and global mail providers.\u003C\u002Fli>\u003Cli>\u003Cstrong>Plaintext Passwords:\u003C\u002Fstrong> Unencrypted authentication passwords stored directly in cleartext.\u003C\u002Fli>\u003C\u002Ful>\u003Ch2>How many individuals or accounts were affected?\u003C\u002Fh2>\u003Cp>Rigorous canonical RFC extraction and deduplication across 2,167,945 database records confirmed \u003Cstrong>1,883,074 unique valid email addresses\u003C\u002Fstrong>.\u003C\u002Fp>\u003Ch2>Technical analysis and security risks\u003C\u002Fh2>\u003Cp>Although Mop.com representatives publicly denied the leak and maintained that passwords were not stored in cleartext, the exfiltrated dataset circulated extensively across threat intelligence communities. The exposure of plaintext credentials creates severe credential stuffing risks due to widespread historical password reuse.\u003C\u002Fp>\u003Ch2>Recommended actions for affected users\u003C\u002Fh2>\u003Cp>Former users of Mop.com should:\u003C\u002Fp>\u003Cul>\u003Cli>Ensure any historical passwords previously utilized on Mop are permanently decommissioned and rotated across all modern online services.\u003C\u002Fli>\u003Cli>Implement multi-factor authentication (MFA) across primary email and enterprise platforms.\u003C\u002Fli>\u003C\u002Ful>","Mop.com Alleged Data Exposure (1.9 Million Email Identifiers)","Mop.com Alleged Data Exposure. 1.9 million email identifiers are reported. Reported data: Email addresses, Passwords. Review the scope, risks, and protective…","\u002Fuploads\u002Flogo\u002Fmop.webp",false,{"name":55,"sector":56,"country":57,"website":57,"websiteArchiveUrl":57,"websiteStatus":57,"websiteCheckedAt":13},"Mop.com","Social Media","",{"success":4,"breaches":59},[60,67,74,81],{"slug":61,"title":62,"companyName":63,"logoUrl":64,"breachDate":65,"affectedCount":66,"affectedCountStatus":21},"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":21},"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":21},"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":21},"spoutible","Spoutible Data Breach","Spoutible","\u002Fuploads\u002Flogo\u002Fspoutible_com.webp","2024-01-31T00:00:00.000Z",207114]