[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$f3ib8xbj0amhkm":3,"$f1bbdozdo4wwn3":62},{"success":4,"breach":5},true,{"_id":6,"name":7,"title":8,"slug":9,"domain":10,"breachDate":11,"addedDate":12,"publishedAt":13,"modifiedDate":13,"contentUpdatedAt":13,"source":14,"sourceUrl":15,"sourceUrls":16,"pwnCount":20,"affectedCount":20,"affectedCountStatus":21,"affectedCountLowerBound":22,"affectedCountUnit":23,"hasEnglishDescription":4,"contentLocale":24,"availableLocales":25,"translations":35,"severity":46,"dataClasses":47,"description":51,"seoTitle":52,"seoDescription":53,"logoUrl":54,"isVerified":4,"isSensitive":4,"isSpamList":55,"isMalware":55,"company":56},"6a6df6459fddb83d2a18c499","CNZZ2012","CNZZ 数据泄露（945,054 条记录）","cnzz-2012","cnzz.com","2012-02-01T00:00:00.000Z","2026-08-01T13:36:05.876Z","2026-10-10T08:23:02.440Z","Contemporary Chinese media reporting, breach-catalog metadata and archived CNZZ database metadata","https:\u002F\u002Fleakedsource.com\u002Fbreaches\u002Fcnzz-data-breach-eb8776d0",[15,17,18,19],"https:\u002F\u002Ffinance.sina.com.cn\u002Fchuangye\u002Finternet\u002F20111227\u002F044011070093.shtml","https:\u002F\u002Fwww.doit.com.cn\u002Fp\u002F104858.html","https:\u002F\u002Fwww.cnzz.com\u002F",945054,"known",null,"accounts","zh",[26,27,24,28,29,30,31,32,33,34],"en","tr","hi","es","ar","fr","bn","pt","ru",{"en":36,"tr":37,"zh":38,"hi":39,"es":40,"ar":41,"fr":42,"bn":43,"pt":44,"ru":45},{"slug":9},{"slug":9},{"slug":9},{"slug":9},{"slug":9},{"slug":9},{"slug":9},{"slug":9},{"slug":9},{"slug":9},"High",[48,49,50],"Usernames","Email addresses","Password hashes","\u003Cp>\u003Cstrong>CNZZ 数据泄露事件\u003C\u002Fstrong>与这家中国网站分析平台的用户数据库泄露有关。已发布的目录条目报告称，受影响的用户记录有 945,054 条，涉及的字段包括用户名、电子邮箱地址和 MD5 密码哈希值。\u003C\u002Fp>\n\u003Ch2>泄露发生于何时？\u003C\u002Fh2>\n\u003Cp>2011年12月，中国多家互联网服务遭遇一波密码泄露，当时的中国媒体报道将 CNZZ 列为受影响的平台之一。后来的泄露事件目录将事件时间记为2012年2月。由于这些来源未能确定最初访问的确切日期，目录仅将时间精确到月份，并未将2012年2月视为已确证的入侵时间。\u003C\u002Fp>\n\u003Ch2>核实情况如何？\u003C\u002Fh2>\n\u003Cp>CNZZ 专属数据库文件的存在，以及当时将该机构与这波泄露事件联系起来的报道，为将该数据集归属于 CNZZ 提供了依据。不过，2012年1月发布的一篇范围更广的后续报道，并未将 CNZZ 单独列入当时官方确认的事件之中。因此，945,054 这一数字是来源报告的总数；公开来源仍未明确入侵的确切日期和最初的访问方式。\u003C\u002Fp>\n\u003Ch2>哪些信息受到影响？\u003C\u002Fh2>\n\u003Cp>据报告，涉及的字段包括用户名、电子邮箱地址和密码哈希值。据称，密码以 MD5 哈希形式存储。如今，MD5 已被认为不足以安全存储密码，而较短或重复使用的密码可能更容易受到离线猜测攻击。\u003C\u002Fp>\n\u003Ch2>受影响的用户应采取哪些措施？\u003C\u002Fh2>\n\u003Cp>如果在其他服务上重复使用了 CNZZ 账户的密码，应将这些账户的密码更换为强度高且各不相同的密码。凡是支持多因素身份验证的服务，都应启用该功能。如果旧电子邮箱收到意料之外的密码重置或账户验证消息，应直接访问相关服务的官方网站进行核查。\u003C\u002Fp>","CNZZ 数据泄露（945,054 条记录） (945.1 千 受影响账户数)","CNZZ 数据泄露（945,054 条记录）. 据报告，涉及945.1 千个账户。 已报告的数据：用户名, 电子邮箱地址, 密码哈希值。 了解影响范围、风险及防护措施。","\u002Fuploads\u002Flogo\u002Fcnzz-official-2012-logo.gif",false,{"name":57,"sector":58,"country":59,"website":10,"websiteArchiveUrl":60,"websiteStatus":61,"websiteCheckedAt":12},"CNZZ","Technology","China","https:\u002F\u002Fweb.archive.org\u002Fweb\u002F20120215204107\u002Fhttp:\u002F\u002Fcnzz.com\u002F","redirects_to_parent_brand",{"success":4,"breaches":63},[64,71,78,85],{"slug":65,"title":66,"companyName":67,"logoUrl":68,"breachDate":69,"affectedCount":70,"affectedCountStatus":21},"dustin-group-2026-data-security-incident","Dustin Group 2026年数据安全事件","Dustin Group AB (publ)","\u002Fuploads\u002Flogo\u002Fdustingroup_com-6aaab48e5041e3a842fe832a-e26a53490c4a5cbe.webp","2026-09-03T00:00:00.000Z",1062841,{"slug":72,"title":73,"companyName":74,"logoUrl":75,"breachDate":76,"affectedCount":77,"affectedCountStatus":21},"splitvpn-2026","SplitVPN 2026 数据泄露","SplitVPN Technologies LLC","\u002Fuploads\u002Flogo\u002Fsplitvpn-2026.webp","2026-07-21T00:00:00.000Z",865336,{"slug":79,"title":80,"companyName":81,"logoUrl":82,"breachDate":83,"affectedCount":22,"affectedCountStatus":84},"brinks-home-2026","Brinks Home 2026年数据泄露事件","Brinks Home","\u002Fuploads\u002Flogo\u002Fbrinks-home-2026.webp","2026-07-20T00:00:00.000Z","not_disclosed",{"slug":86,"title":87,"companyName":88,"logoUrl":89,"breachDate":90,"affectedCount":22,"affectedCountStatus":84},"hugging-face-2026","Hugging Face 2026 年安全入侵事件","Hugging Face","\u002Fuploads\u002Flogo\u002Fhuggingface_co.svg","2026-07-16T00:00:00.000Z"]