[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$f3mren0dsr5jp3":3,"$fgdr9ntz4mtvi":62},{"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":53,"seoTitle":54,"seoDescription":55,"logoUrl":56,"isVerified":4,"isSensitive":57,"isSpamList":57,"isMalware":57,"company":58},"6aad3834f9ea9ef5005ea9c9","MuMaYi 2011","MuMaYi Data Breach","mumayi-2011","mumayi.com","2011-05-11T00:00:00.000Z","2026-09-18T13:10:12.109Z",null,"2026-10-10T10:26:26.049Z","MuMaYi Android application market and forum database breach","http:\u002F\u002Fwww.mumayi.com\u002F",[16,18,19],"https:\u002F\u002Fsynscan.net\u002F","https:\u002F\u002Fransomlook.io\u002F",127515,"known","unknown","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},"High",[47,48,49,50,51,52],"Email addresses","Usernames","Passwords","IP addresses","Dates of birth","Genders","\u003Cp>\u003Cstrong>The 2011 MuMaYi (木蚂蚁) data breach\u003C\u002Fstrong> occurred in May 2011 when the Discuz! community and Android application repository database of \u003Cstrong>MuMaYi\u003C\u002Fstrong> (\u003Ccode>mumayi.com\u003C\u002Fcode>), a leading Chinese Android app marketplace and custom ROM forum, was breached and leaked online.\u003C\u002Fp>\u003Ch2>What information was affected in the MuMaYi incident?\u003C\u002Fh2>\u003Cp>The leaked member table (\u003Ccode>mumayicdb_members\u003C\u002Fcode>) encompasses developers, modders, and mobile app users. The incident compromised records for \u003Cstrong>127,515 unique individuals\u003C\u002Fstrong>, exposing:\u003C\u002Fp>\u003Cul>\u003Cli>\u003Cstrong>Account Identifiers:\u003C\u002Fstrong> Community usernames and numerical identifiers (uid).\u003C\u002Fli>\u003Cli>\u003Cstrong>Contact Credentials:\u003C\u002Fstrong> Canonical email addresses across domestic Chinese providers (qq.com, 163.com, 126.com, sina.com, sohu.com) and international mail services.\u003C\u002Fli>\u003Cli>\u003Cstrong>Authentication Secrets:\u003C\u002Fstrong> MD5 password hashes and security question tokens (secques).\u003C\u002Fli>\u003Cli>\u003Cstrong>Network Telemetry:\u003C\u002Fstrong> Registration IP addresses (regip) and last login IP addresses (lastip).\u003C\u002Fli>\u003Cli>\u003Cstrong>Demographic Records:\u003C\u002Fstrong> Dates of birth (bday) and gender.\u003C\u002Fli>\u003C\u002Ful>\u003Ch2>How many accounts were affected?\u003C\u002Fh2>\u003Cp>Rigorous RFC canonical parsing and deduplication confirmed \u003Cstrong>127,515 unique valid email addresses\u003C\u002Fstrong>.\u003C\u002Fp>\u003Ch2>Technical analysis and security risks\u003C\u002Fh2>\u003Cp>The exposure stems from an exploited vulnerability in the Discuz! forum installation. MD5 password hashes are vulnerable to modern GPU-based cracking, facilitating credential-stuffing campaigns across personal webmail and related platform accounts.\u003C\u002Fp>\u003Ch2>Recommended actions for affected users\u003C\u002Fh2>\u003Cp>Former members of MuMaYi should:\u003C\u002Fp>\u003Cul>\u003Cli>Immediately update passwords across any active email or web accounts where their old forum password was reused.\u003C\u002Fli>\u003Cli>Enable two-factor authentication (2FA) across all critical services.\u003C\u002Fli>\u003C\u002Ful>","MuMaYi Data Breach (127.5 Thousand Reported Records)","MuMaYi Data Breach. 127.5 thousand records are reported. Reported data: Email addresses, Usernames, Passwords. Review the scope, risks, and protective steps.","\u002Fuploads\u002Flogo\u002Fmumayi.webp",false,{"name":59,"sector":60,"country":61,"website":61,"websiteArchiveUrl":61,"websiteStatus":61,"websiteCheckedAt":13},"MuMaYi","Technology","",{"success":4,"breaches":63},[64,71,78,85],{"slug":65,"title":66,"companyName":67,"logoUrl":68,"breachDate":69,"affectedCount":70,"affectedCountStatus":21},"dustin-group-2026-data-security-incident","Dustin Group 2026 Data Security Incident","Dustin Group AB (publ)","\u002Fuploads\u002Flogo\u002Fdustingroup_com-6aaab48e5041e3a842fe832a-e26a53490c4a5cbe.webp","2026-09-03T00:00:00.000Z",1062841,{"slug":72,"title":73,"companyName":74,"logoUrl":75,"breachDate":76,"affectedCount":77,"affectedCountStatus":21},"splitvpn-2026","SplitVPN 2026 Data Breach","SplitVPN Technologies LLC","\u002Fuploads\u002Flogo\u002Fsplitvpn-2026.webp","2026-07-21T00:00:00.000Z",865336,{"slug":79,"title":80,"companyName":81,"logoUrl":82,"breachDate":83,"affectedCount":13,"affectedCountStatus":84},"brinks-home-2026","Brinks Home 2026 Data Breach","Brinks Home","\u002Fuploads\u002Flogo\u002Fbrinks-home-2026.webp","2026-07-20T00:00:00.000Z","not_disclosed",{"slug":86,"title":87,"companyName":88,"logoUrl":89,"breachDate":90,"affectedCount":13,"affectedCountStatus":84},"hugging-face-2026","Hugging Face 2026 Security Breach","Hugging Face","\u002Fuploads\u002Flogo\u002Fhuggingface_co.svg","2026-07-16T00:00:00.000Z"]