[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$f1dfq1osaovstv":3,"$f2eium650zlbri":61},{"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":52,"seoTitle":53,"seoDescription":54,"logoUrl":55,"isVerified":4,"isSensitive":56,"isSpamList":56,"isMalware":56,"company":57},"6aad3d809eee9fa5e7b6b766","MSPAForums 2016","MSPAForums Data Breach","mspaforums-2016","mspaforums.com","2016-03-19T00:00:00.000Z","2026-09-18T13:32:48.511Z",null,"2026-10-10T10:26:26.036Z","MSPAForums Homestuck and MS Paint Adventures community database breach","https:\u002F\u002Fwww.homestuck.com\u002F",[16,18,19],"https:\u002F\u002Fsynscan.net\u002F","https:\u002F\u002Fransomlook.io\u002F",180680,"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],"Email addresses","Usernames","Passwords","Password salts","IP addresses","\u003Cp>\u003Cstrong>The 2016 MSPAForums data breach\u003C\u002Fstrong> occurred in March 2016 when the official community and discussion forums of \u003Cstrong>MSPAForums\u003C\u002Fstrong> (\u003Ccode>mspaforums.com\u003C\u002Fcode>), the online hub for Andrew Hussie's popular webcomic phenomena \u003Cem>Homestuck\u003C\u002Fem> and \u003Cem>MS Paint Adventures\u003C\u002Fem>, were compromised and leaked online.\u003C\u002Fp>\u003Ch2>What information was affected in the MSPAForums incident?\u003C\u002Fh2>\u003Cp>The extracted vBulletin forum credential export (\u003Ccode>MSPAforums.com 180k.txt\u003C\u002Fcode>) contained account records for fandom participants. Compromised records for \u003Cstrong>180,680 unique registered accounts\u003C\u002Fstrong> include:\u003C\u002Fp>\u003Cul>\u003Cli>\u003Cstrong>Account Identifiers:\u003C\u002Fstrong> Member usernames.\u003C\u002Fli>\u003Cli>\u003Cstrong>Contact Credentials:\u003C\u002Fstrong> Canonical email addresses.\u003C\u002Fli>\u003Cli>\u003Cstrong>Authentication Data:\u003C\u002Fstrong> Passwords hashed using MD5 with cryptographic salt strings.\u003C\u002Fli>\u003Cli>\u003Cstrong>Network Identifiers:\u003C\u002Fstrong> Registration and connection IP addresses.\u003C\u002Fli>\u003C\u002Ful>\u003Ch2>How many accounts were affected?\u003C\u002Fh2>\u003Cp>Rigorous RFC canonical parsing and deduplication across 180,930 lines confirmed \u003Cstrong>180,680 unique valid email addresses\u003C\u002Fstrong>.\u003C\u002Fp>\u003Ch2>Technical analysis and security risks\u003C\u002Fh2>\u003Cp>The dump originated from a vBulletin discussion forum. Salted MD5 hashes are susceptible to offline GPU dictionary attacks. Given high credential reuse rates among fandom community members, exposed credentials facilitate credential stuffing attacks across external platforms.\u003C\u002Fp>\u003Ch2>Recommended actions for affected users\u003C\u002Fh2>\u003Cp>Community members who maintained an account on MSPAForums should:\u003C\u002Fp>\u003Cul>\u003Cli>Immediately update passwords on other services where identical credentials might still be active.\u003C\u002Fli>\u003Cli>Enable two-factor authentication (2FA) wherever possible.\u003C\u002Fli>\u003C\u002Ful>","MSPAForums Data Breach (180.7 Thousand Reported Records)","MSPAForums Data Breach. 180.7 thousand records are reported. Reported data: Email addresses, Usernames, Passwords. Review the scope, risks, and protective…","\u002Fuploads\u002Flogo\u002Fmspaforums.webp",false,{"name":58,"sector":59,"country":60,"website":60,"websiteArchiveUrl":60,"websiteStatus":60,"websiteCheckedAt":13},"MSPAForums","Online Community","",{"success":4,"breaches":62},[63,70,77,84],{"slug":64,"title":65,"companyName":66,"logoUrl":67,"breachDate":68,"affectedCount":69,"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":71,"title":72,"companyName":73,"logoUrl":74,"breachDate":75,"affectedCount":76,"affectedCountStatus":21},"hackernewbie-2022","HackerNewbie Data Breach","HackerNewbie","\u002Fuploads\u002Flogo\u002Fhacker_newbie_org.webp","2022-09-10T00:00:00.000Z",28326,{"slug":78,"title":79,"companyName":80,"logoUrl":81,"breachDate":82,"affectedCount":83,"affectedCountStatus":21},"thctalk-2022","THCtalk Data Breach","THCtalk","\u002Fuploads\u002Flogo\u002Fthctalk.webp","2022-08-19T00:00:00.000Z",82013,{"slug":85,"title":86,"companyName":87,"logoUrl":88,"breachDate":89,"affectedCount":90,"affectedCountStatus":21},"trackitt-2022","Trackitt Data Breach","Trackitt","\u002Fuploads\u002Flogo\u002Ftrackitt_com.webp","2022-07-08T00:00:00.000Z",428360]