[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$f2s947eie1ovm9":3},{"success":4,"breach":5},true,{"_id":6,"name":7,"title":8,"slug":7,"domain":9,"breachDate":10,"addedDate":11,"modifiedDate":12,"contentUpdatedAt":12,"source":13,"sourceUrl":14,"sourceUrls":15,"pwnCount":16,"affectedCount":16,"affectedCountStatus":17,"affectedCountLowerBound":18,"affectedCountUnit":19,"hasEnglishDescription":4,"severity":20,"dataClasses":21,"description":26,"seoTitle":14,"seoTitleEn":27,"seoDescription":14,"seoDescriptionEn":28,"logoUrl":29,"isVerified":4,"isSensitive":30,"isSpamList":30,"isMalware":30,"company":31},"68e3266eda11adda4882523e","insanelyi","Insanelyi Data Breach","insanelyi.com","2014-07-22T00:00:00.000Z","2014-07-22T22:56:15.000Z","2026-07-29T15:45:51.001Z","Authenticated attributed breach corpus with a local email-only subset","",[],104097,"known",null,"email_identifiers","High",[22,23,24,25],"Email addresses","Passwords","Usernames","Website activity","\u003Cp>\u003Cstrong>The Insanelyi 2014 data breach\u003C\u002Fstrong> covers account data attributed to the former Insanelyi forum, which focused on iOS software and device customization. A verified breach index dates the event to 22 July 2014 and reports 104,097 unique email addresses in the attributed corpus. According to the index analysis, the data types are email addresses, usernames, website activity, and salted MD5 password hashes.\u003C\u002Fp>\n\n\u003Cp>The 104,097 value is a unique-email count, not a count of unique people, active accounts, or file rows. A production email-only job processed 104,011 lines and produced 103,995 unique emails in the live index. These three measures are different and are not added together. The local job processed no username, password-hash, or website-activity column, so those fields rely solely on the external corpus analysis.\u003C\u002Fp>\n\n\u003Ch2>Evidence and privacy boundary\u003C\u002Fh2>\n\u003Cp>Manual review found no first-party notice or reliable independent technical report describing the incident. A contemporary article linked from the breach index concerns a different iOS software repository and does not name Insanelyi, so it was not used as evidence for an attacker or access method. The public source also does not disclose the exact schema behind the “website activity” field.\u003C\u002Fp>\n\n\u003Cp>An email match alone does not prove that a person used the forum, customized a particular device, viewed particular content, owns a listed username today, or still has an active account. The source does not report legal names, phone numbers, physical addresses, payment data, private messages, or IP addresses. A salted MD5 hash is not a plaintext password, but an old, short, or reused password may still present a risk under current standards.\u003C\u002Fp>\n\n\u003Ch2>Safe next steps and archive link\u003C\u002Fh2>\n\u003Cp>If a person independently knows the password used on this forum in 2014 and still uses the same or a similar password on another active account, only that reused password should be replaced with a unique one, and multifactor authentication should be enabled on the associated email account. The current domain now leads to a sale page rather than the historical forum, so the company link points to a Wayback Machine capture from 25 June 2014. The archive is historical context, not a current support or security channel.\u003C\u002Fp>","Insanelyi 2014 Data Breach (104.1 Thousand Email Identifiers)","The Insanelyi breach included 104,097 unique emails. Review the local email subset, salted-MD5 hashes, and evidence boundaries.","\u002Fuploads\u002Flogo\u002Finsanelyi_com.webp",false,{"name":32,"sector":33,"country":34,"website":9,"websiteArchiveUrl":35,"websiteStatus":36,"websiteCheckedAt":18},"Insanelyi","Online Forum","United States","https:\u002F\u002Fweb.archive.org\u002Fweb\u002F20140625125213id_\u002Fhttp:\u002F\u002Finsanelyi.com\u002F","archived"]