[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$f1lh5h5j3hd0h3":3,"$f3v1qsdoc7cx5w":59},{"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":50,"seoTitle":51,"seoDescription":52,"logoUrl":53,"isVerified":4,"isSensitive":54,"isSpamList":54,"isMalware":54,"company":55},"6aadca8ae186c993dbeee392","JeepForum 2016","JeepForum Data Breach","jeepforum-2016","jeepforum.com","2016-02-01T00:00:00.000Z","2026-09-18T23:34:34.010Z",null,"2026-10-10T08:26:39.865Z","JeepForum VerticalScope automotive enthusiast community forum database breach","https:\u002F\u002Fwww.jeepforum.com\u002F",[16,18,19],"https:\u002F\u002Fkrebsonsecurity.com\u002F2017\u002F11\u002F2nd-breach-at-verticalscope-impacts\u002F","https:\u002F\u002Fen.wikipedia.org\u002Fwiki\u002FJeep",507784,"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],"Email addresses","Usernames","Passwords","\u003Cp>\u003Cstrong>The 2016 JeepForum data breach\u003C\u002Fstrong> occurred in February 2016 when \u003Cstrong>JeepForum\u003C\u002Fstrong> (\u003Ccode>jeepforum.com\u003C\u002Fcode>), the premier online enthusiast community for Jeep and off-road vehicle owners operated by VerticalScope, was breached as part of a massive systemic intrusion affecting hundreds of VerticalScope forum properties.\u003C\u002Fp>\u003Ch2>What information was affected in the JeepForum incident?\u003C\u002Fh2>\u003Cp>Officially acknowledged by VerticalScope and investigated by KrebsOnSecurity, the compromised database for \u003Cstrong>507,784 unique accounts\u003C\u002Fstrong> encompasses:\u003C\u002Fp>\u003Cul>\u003Cli>\u003Cstrong>Authentication Credentials:\u003C\u002Fstrong> Valid canonical email addresses, forum usernames, and password hashes with cryptographic salts.\u003C\u002Fli>\u003Cli>\u003Cstrong>Plaintext (Cracked) Passwords:\u003C\u002Fstrong> Passwords cracked from original hashes using dictionary and brute-force cracking methodologies.\u003C\u002Fli>\u003C\u002Ful>\u003Ch2>How many accounts were affected?\u003C\u002Fh2>\u003Cp>Rigorous canonical RFC extraction and deduplication across 853,569 database rows confirmed \u003Cstrong>507,784 unique valid email addresses\u003C\u002Fstrong>.\u003C\u002Fp>\u003Ch2>Technical analysis and security risks\u003C\u002Fh2>\u003Cp>Attackers compromised the underlying forum infrastructure, facilitating the mass exfiltration and subsequent cracking of stored credentials. The broad availability of cracked plaintext passwords enables automated credential stuffing across diverse corporate and personal online accounts.\u003C\u002Fp>\u003Ch2>Recommended actions for affected users\u003C\u002Fh2>\u003Cp>Current and former members of JeepForum should:\u003C\u002Fp>\u003Cul>\u003Cli>Immediately rotate credentials across any platforms where identical or similar passwords were ever reused.\u003C\u002Fli>\u003Cli>Implement multi-factor authentication (MFA\u002F2FA) on all critical online services.\u003C\u002Fli>\u003C\u002Ful>","JeepForum Data Breach (507.8 Thousand Reported Records)","JeepForum Data Breach. 507.8 thousand records are reported. Reported data: Email addresses, Usernames, Passwords. Review the scope, risks, and protective steps.","\u002Fuploads\u002Flogo\u002Fjeepforum.webp",false,{"name":56,"sector":57,"country":58,"website":58,"websiteArchiveUrl":58,"websiteStatus":58,"websiteCheckedAt":13},"JeepForum","Online Community","",{"success":4,"breaches":60},[61,68,75,82],{"slug":62,"title":63,"companyName":64,"logoUrl":65,"breachDate":66,"affectedCount":67,"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":69,"title":70,"companyName":71,"logoUrl":72,"breachDate":73,"affectedCount":74,"affectedCountStatus":21},"hackernewbie-2022","HackerNewbie Data Breach","HackerNewbie","\u002Fuploads\u002Flogo\u002Fhacker_newbie_org.webp","2022-09-10T00:00:00.000Z",28326,{"slug":76,"title":77,"companyName":78,"logoUrl":79,"breachDate":80,"affectedCount":81,"affectedCountStatus":21},"thctalk-2022","THCtalk Data Breach","THCtalk","\u002Fuploads\u002Flogo\u002Fthctalk.webp","2022-08-19T00:00:00.000Z",82013,{"slug":83,"title":84,"companyName":85,"logoUrl":86,"breachDate":87,"affectedCount":88,"affectedCountStatus":21},"trackitt-2022","Trackitt Data Breach","Trackitt","\u002Fuploads\u002Flogo\u002Ftrackitt_com.webp","2022-07-08T00:00:00.000Z",428360]