[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$f2fr1q5h6w2vne":3,"$f3ptsuzirx1d1l":60},{"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":51,"seoTitle":52,"seoDescription":53,"logoUrl":54,"isVerified":55,"isSensitive":55,"isSpamList":55,"isMalware":55,"company":56},"6aadc98006cc701ee0d89088","Lupaworld 2016","Lupaworld Alleged Data Exposure","lupaworld-2016","lupaworld.com","2016-11-23T00:00:00.000Z","2026-09-18T23:30:07.822Z",null,"2026-10-10T08:42:32.361Z","Lupaworld Chinese open source Linux community forum database breach","https:\u002F\u002Fweb.archive.org\u002Fweb\u002F20120119041235\u002Fhttp:\u002F\u002Fwww.lupaworld.com\u002F",[16,18,19],"https:\u002F\u002Fweb.archive.org\u002Fweb\u002F20220130171918\u002Fhttps:\u002F\u002Fraidforums.com\u002FAnnouncement-Database-Index-CLICK-ME","https:\u002F\u002Fgithub.com\u002F",433374,"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},"High",[47,48,49,50],"Email addresses","Usernames","Passwords","IP addresses","\u003Cp>\u003Cstrong>The 2016 Lupaworld data breach\u003C\u002Fstrong> occurred in November 2016 when the forum database of \u003Cstrong>Lupaworld\u003C\u002Fstrong> (\u003Ccode>lupaworld.com\u003C\u002Fcode>), historically one of the most prominent open-source and Linux developer community platforms in China (LUPA Open Source Community), was compromised by threat actors.\u003C\u002Fp>\u003Ch2>What information was affected in the Lupaworld incident?\u003C\u002Fh2>\u003Cp>The leaked forum export (\u003Ccode>lupaworld_com_523926 Users.txt\u003C\u002Fcode>) contains member registration credentials and access logs. Impacted records for \u003Cstrong>433,374 unique accounts\u003C\u002Fstrong> include:\u003C\u002Fp>\u003Cul>\u003Cli>\u003Cstrong>Authentication Secrets:\u003C\u002Fstrong> Validated canonical email addresses, forum usernames, and password hashes generated using MD5 with a 6-character salt.\u003C\u002Fli>\u003Cli>\u003Cstrong>Network Identifiers:\u003C\u002Fstrong> Member registration and session IP addresses.\u003C\u002Fli>\u003C\u002Ful>\u003Ch2>How many accounts were affected?\u003C\u002Fh2>\u003Cp>Rigorous canonical RFC email parsing and deduplication across 523,926 database rows confirmed \u003Cstrong>433,374 unique valid email addresses\u003C\u002Fstrong>.\u003C\u002Fp>\u003Ch2>Technical analysis and security risks\u003C\u002Fh2>\u003Cp>While passwords utilized salting, the underlying MD5 hashing algorithm is cryptographically weak against modern GPU-accelerated hash recovery and dictionary attacks. The exposure of email and username pairs creates significant credential stuffing exposure across other developer and web platforms.\u003C\u002Fp>\u003Ch2>Recommended actions for affected users\u003C\u002Fh2>\u003Cp>Former users and contributors of Lupaworld should:\u003C\u002Fp>\u003Cul>\u003Cli>Immediately update passwords on any current accounts where identical or similar credentials were ever utilized.\u003C\u002Fli>\u003Cli>Enable multi-factor authentication (MFA\u002F2FA) on critical accounts including email and software repositories.\u003C\u002Fli>\u003C\u002Ful>","Lupaworld Alleged Data Exposure (433.4 Thousand Email Identifiers)","Lupaworld Alleged Data Exposure. 433.4 thousand email identifiers are reported. Reported data: Email addresses, Usernames, Passwords. Review the scope, risks…","\u002Fuploads\u002Flogo\u002Flupaworld.webp",false,{"name":57,"sector":58,"country":59,"website":59,"websiteArchiveUrl":59,"websiteStatus":59,"websiteCheckedAt":13},"Lupaworld","Online Community","",{"success":4,"breaches":61},[62,69,76,83],{"slug":63,"title":64,"companyName":65,"logoUrl":66,"breachDate":67,"affectedCount":68,"affectedCountStatus":21},"cyberphoenix-community-2024","CyberPhoenix 2024 Data Breach","CyberPhoenix Community Veri İhlali (2024)","\u002Fuploads\u002Flogo\u002Fcyberphoenix-community-2024.webp","2024-09-19T00:00:00.000Z",419000,{"slug":70,"title":71,"companyName":72,"logoUrl":73,"breachDate":74,"affectedCount":75,"affectedCountStatus":21},"hackernewbie-2022","HackerNewbie Data Breach","HackerNewbie","\u002Fuploads\u002Flogo\u002Fhacker_newbie_org.webp","2022-09-10T00:00:00.000Z",28326,{"slug":77,"title":78,"companyName":79,"logoUrl":80,"breachDate":81,"affectedCount":82,"affectedCountStatus":21},"thctalk-2022","THCtalk Data Breach","THCtalk","\u002Fuploads\u002Flogo\u002Fthctalk.webp","2022-08-19T00:00:00.000Z",82013,{"slug":84,"title":85,"companyName":86,"logoUrl":87,"breachDate":88,"affectedCount":89,"affectedCountStatus":21},"trackitt-2022","Trackitt Data Breach","Trackitt","\u002Fuploads\u002Flogo\u002Ftrackitt_com.webp","2022-07-08T00:00:00.000Z",428360]