[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$f2t78mzfon6dv0":3,"$f34w03r8ll28gl":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":4,"isSensitive":55,"isSpamList":55,"isMalware":55,"company":56},"6aad0d20221f974eb5f7921b","AutoHotkey 2015","AutoHotkey Data Breach","autohotkey-2015","autohotkey.com","2015-12-01T00:00:00.000Z","2026-09-18T10:06:24.016Z",null,"2026-10-10T10:43:41.207Z","AutoHotkey forum database dump & breach intelligence","https:\u002F\u002Fwww.autohotkey.com\u002F",[16,18,19],"https:\u002F\u002Fleakcheck.io\u002F","https:\u002F\u002Fsynscan.net\u002F",44417,"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},"Medium",[47,48,49,50],"Email addresses","Passwords","Usernames","IP addresses","\u003Cp>\u003Cstrong>The 2015 AutoHotkey data breach\u003C\u002Fstrong> occurred when unauthorized threat actors breached the community forum infrastructure of \u003Cstrong>AutoHotkey\u003C\u002Fstrong> (\u003Ccode>autohotkey.com\u003C\u002Fcode>), the renowned open-source automation scripting language for Windows. The incident compromised forum member profile information, registered email addresses, connection IP addresses, and salted password hashes.\u003C\u002Fp>\u003Ch2>What information was affected in the AutoHotkey incident?\u003C\u002Fh2>\u003Cp>The compromised forum export contains member identity records from the project's developer community. The leak impacted \u003Cstrong>44,417 unique user accounts\u003C\u002Fstrong>, exposing the following data categories:\u003C\u002Fp>\u003Cul>\u003Cli>\u003Cstrong>Account Identifiers:\u003C\u002Fstrong> Community usernames.\u003C\u002Fli>\u003Cli>\u003Cstrong>Contact Credentials:\u003C\u002Fstrong> Canonical email addresses.\u003C\u002Fli>\u003Cli>\u003Cstrong>Network Data:\u003C\u002Fstrong> Registration and login IP addresses.\u003C\u002Fli>\u003Cli>\u003Cstrong>Authentication Credentials:\u003C\u002Fstrong> Invision Power Board (IPBoard) cryptographic password hashes alongside respective salt values.\u003C\u002Fli>\u003C\u002Ful>\u003Ch2>How many accounts were affected?\u003C\u002Fh2>\u003Cp>Canonical extraction and deduplication of the database dump confirmed \u003Cstrong>44,417 unique canonical email addresses\u003C\u002Fstrong> across 88,871 raw forum member rows.\u003C\u002Fp>\u003Ch2>Technical analysis and security risks\u003C\u002Fh2>\u003Cp>The exposure stems from a backend SQL database dump of the forum member directory. Although password records are protected by salts and hashes, common passwords remain vulnerable to offline dictionary and rainbow table cracking. Furthermore, the developer-centric nature of the community makes affected email addresses attractive targets for spear-phishing and social engineering attacks.\u003C\u002Fp>\u003Ch2>Recommended actions for affected users\u003C\u002Fh2>\u003Cp>Members of the AutoHotkey community should:\u003C\u002Fp>\u003Cul>\u003Cli>Ensure that any password utilized on the AutoHotkey forum during or prior to 2015 is discontinued across all online platforms.\u003C\u002Fli>\u003Cli>Remain vigilant regarding targeted phishing attempts referencing scripting libraries, software updates, or IT tooling.\u003C\u002Fli>\u003Cli>Enforce two-factor authentication (2FA \u002F MFA) on personal email and code hosting platforms.\u003C\u002Fli>\u003C\u002Ful>","AutoHotkey Data Breach (44.4 Thousand Reported Records)","AutoHotkey Data Breach. 44.4 thousand records are reported. Reported data: Email addresses, Passwords, Usernames. Review the scope, risks, and protective steps.","\u002Fuploads\u002Flogo\u002Fautohotkey_com.webp",false,{"name":57,"sector":58,"country":59,"website":59,"websiteArchiveUrl":59,"websiteStatus":59,"websiteCheckedAt":13},"AutoHotkey","Technology","",{"success":4,"breaches":61},[62,69,76,83],{"slug":63,"title":64,"companyName":65,"logoUrl":66,"breachDate":67,"affectedCount":68,"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":70,"title":71,"companyName":72,"logoUrl":73,"breachDate":74,"affectedCount":75,"affectedCountStatus":21},"splitvpn-2026","SplitVPN 2026 Data Breach","SplitVPN Technologies LLC","\u002Fuploads\u002Flogo\u002Fsplitvpn-2026.webp","2026-07-21T00:00:00.000Z",865336,{"slug":77,"title":78,"companyName":79,"logoUrl":80,"breachDate":81,"affectedCount":13,"affectedCountStatus":82},"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":84,"title":85,"companyName":86,"logoUrl":87,"breachDate":88,"affectedCount":13,"affectedCountStatus":82},"hugging-face-2026","Hugging Face 2026 Security Breach","Hugging Face","\u002Fuploads\u002Flogo\u002Fhuggingface_co.svg","2026-07-16T00:00:00.000Z"]