[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$fzu0wxxyfhg1d":3,"$f3n654eun2hs8c":59},{"success":4,"breach":5},true,{"_id":6,"name":7,"title":8,"slug":7,"domain":9,"breachDate":10,"addedDate":11,"publishedAt":12,"modifiedDate":12,"contentUpdatedAt":12,"source":13,"sourceUrl":14,"sourceUrls":15,"pwnCount":16,"affectedCount":16,"affectedCountStatus":17,"affectedCountLowerBound":18,"affectedCountUnit":19,"hasEnglishDescription":4,"contentLocale":20,"availableLocales":21,"translations":31,"severity":42,"dataClasses":43,"description":48,"seoTitle":49,"seoDescription":50,"logoUrl":51,"isVerified":4,"isSensitive":52,"isSpamList":52,"isMalware":52,"company":53},"68e3266eda11adda4882523e","insanelyi","Insanelyi 2014年数据泄露","insanelyi.com","2014-07-22T00:00:00.000Z","2014-07-22T22:56:15.000Z","2026-10-10T08:38:58.881Z","Authenticated attributed breach corpus with a local email-only subset","",[],104097,"known",null,"email_identifiers","zh",[22,23,20,24,25,26,27,28,29,30],"en","tr","hi","es","ar","fr","bn","pt","ru",{"en":32,"tr":33,"zh":34,"hi":35,"es":36,"ar":37,"fr":38,"bn":39,"pt":40,"ru":41},{"slug":7},{"slug":7},{"slug":7},{"slug":7},{"slug":7},{"slug":7},{"slug":7},{"slug":7},{"slug":7},{"slug":7},"High",[44,45,46,47],"Email addresses","Passwords","Usernames","Website activity","\u003Cp>\u003Cstrong>Insanelyi 2014年数据泄露事件\u003C\u002Fstrong>涉及被认为来自原 Insanelyi 论坛的账户数据。该论坛主要讨论 iOS 软件和设备定制。一个经核验的数据泄露索引将事件日期记为2014年7月22日，并称这批数据包含104,097个唯一电子邮箱地址。根据该索引的分析，数据类型包括电子邮箱地址、用户名、网站活动和加盐 MD5 密码哈希。\u003C\u002Fp>\n\n\u003Cp>104,097是去重后的电子邮箱地址数量，而不是不同个人的数量、活跃账户数或文件行数。生产环境中一个仅处理邮箱数据的任务处理了104,011行数据，并在在线索引中生成了103,995个唯一电子邮箱地址。这三个统计值衡量的对象不同，不能相加。本地任务未处理任何用户名、密码哈希或网站活动列，因此对这些字段的描述完全依据外部数据集分析。\u003C\u002Fp>\n\n\u003Ch2>证据与隐私边界\u003C\u002Fh2>\n\u003Cp>人工审查未发现涉事方发布的通知，也未找到描述此次事件的可靠独立技术报告。数据泄露索引中链接的一篇同期文章涉及另一个 iOS 软件仓库，并未提及 Insanelyi，因此未将其用作判断攻击者或访问方式的证据。公开来源也未披露“网站活动”字段的具体数据结构。\u003C\u002Fp>\n\n\u003Cp>仅凭电子邮箱地址匹配，不能证明某人曾使用该论坛、定制过某台设备、浏览过特定内容、如今仍拥有所列用户名，或仍有活跃账户。来源未报告法定姓名、电话号码、实际地址、支付数据、私信或 IP 地址。加盐 MD5 哈希并非明文密码，但按照现行标准，使用已久、长度较短或重复使用的密码仍可能存在风险。\u003C\u002Fp>\n\n\u003Ch2>安全后续措施与存档链接\u003C\u002Fh2>\n\u003Cp>如果本人能自行确认2014年在该论坛使用的密码，并且仍在其他活跃账户上使用相同或类似的密码，则只应将该重复使用的密码替换为该账户专用、且不与其他账户重复的密码，并为关联的电子邮箱账户启用多因素身份验证。该域名目前指向出售页面，而非过去的论坛，因此公司链接指向2014年6月25日的 Wayback Machine 网页存档。该存档仅提供历史背景，并非当前的支持或安全渠道。\u003C\u002Fp>","Insanelyi 2014年数据泄露 (104.1 千 电子邮件标识符)","Insanelyi 2014年数据泄露. 据报告，涉及104.1 千个电子邮件标识符。 已报告的数据：电子邮箱地址, 密码, 用户名。 了解影响范围、风险及防护措施。","\u002Fuploads\u002Flogo\u002Finsanelyi_com.webp",false,{"name":54,"sector":55,"country":56,"website":9,"websiteArchiveUrl":57,"websiteStatus":58,"websiteCheckedAt":18},"Insanelyi","Online Forum","United States","https:\u002F\u002Fweb.archive.org\u002Fweb\u002F20140625125213id_\u002Fhttp:\u002F\u002Finsanelyi.com\u002F","archived",{"success":4,"breaches":60},[61,68,75,82],{"slug":62,"title":63,"companyName":64,"logoUrl":65,"breachDate":66,"affectedCount":67,"affectedCountStatus":17},"kaspersky-club","Kaspersky Club 论坛2024年数据泄露事件","Kaspersky Club","\u002Fuploads\u002Flogo\u002Fkasperskyclub_ru.webp","2024-03-24T00:00:00.000Z",55971,{"slug":69,"title":70,"companyName":71,"logoUrl":72,"breachDate":73,"affectedCount":74,"affectedCountStatus":17},"kiwifarms","Kiwi Farms 2019年数据泄露","Kiwi Farms","\u002Fuploads\u002Flogo\u002Fkiwifarms_net.webp","2019-09-10T00:00:00.000Z",4606,{"slug":76,"title":77,"companyName":78,"logoUrl":79,"breachDate":80,"affectedCount":81,"affectedCountStatus":17},"lolzteam","Lolzteam 数据泄露","Lolzteam","\u002Fuploads\u002Flogo\u002Flolzteam_net.webp","2018-05-13T00:00:00.000Z",398011,{"slug":83,"title":84,"companyName":85,"logoUrl":86,"breachDate":87,"affectedCount":88,"affectedCountStatus":17},"ipmart","iPmart 2015年数据泄露事件","iPmart","\u002Fuploads\u002Flogo\u002Fipmart_forum_com.webp","2015-07-01T00:00:00.000Z",2460787]