[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$fubeawn064n9t":3,"$f1e516w8iwk6yk":60},{"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":20,"affectedCountUnit":22,"hasEnglishDescription":4,"contentLocale":23,"availableLocales":24,"translations":34,"severity":45,"dataClasses":46,"description":49,"seoTitle":8,"seoDescription":50,"logoUrl":51,"isVerified":4,"isSensitive":4,"isSpamList":52,"isMalware":52,"company":53},"6a669c6d932e5f055682f97c","KlueOAuth2026","Klue 2026 年 OAuth 供应链数据泄露","klue-oauth-2026","klue.com","2026-06-11T00:00:00.000Z","2026-07-26T23:46:53.292Z","2026-10-09T21:22:52.637Z","Official notices from affected institutions","https:\u002F\u002Fklue.com\u002Fblog\u002Fcrowdstrike-investigation-summary-and-security-improvements",[15,17,18,19],"https:\u002F\u002Fklue.com\u002Fblog\u002Fan-update-on-recent-klue-security-incident","https:\u002F\u002Fwww.bleepingcomputer.com\u002Fnews\u002Fsecurity\u002Fklue-oauth-breach-victim-list-grows-as-icarus-hackers-claim-attack\u002F","https:\u002F\u002Fklue.com\u002F",null,"unknown","accounts","zh",[25,26,23,27,28,29,30,31,32,33],"en","tr","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},"Unknown",[47,48],"Third-party integration credentials","Authentication tokens","\u003Cp>\u003Cstrong>Klue 2026 年 OAuth 供应链数据泄露事件\u003C\u002Fstrong>涉及在该公司的第三方集成服务中未经授权执行代码，以及收集相连平台的凭据。据 Klue 发布的调查摘要，威胁行为者于 2026年6月11日利用此前已失陷的 GitHub 个人访问令牌，将代码植入集成服务，收集第三方集成凭据，其中包括 Salesforce OAuth 访问令牌和刷新令牌。Klue 未披露受影响的客户、环境、账户或令牌总数，生产环境中也没有与此事件相关的本地个人级数据集。\u003C\u002Fp>\n\n\u003Ch2>事件的时间线和影响范围是什么？\u003C\u002Fh2>\n\u003Cp>Salesforce 于 6月12日通知 Klue，称发现源自 Klue API 集成服务的可疑第三方活动。Klue 表示，当天上午已停用受影响的 GKE pods 和已失陷的 GitHub 令牌，并轮换了 OAuth 凭据。该公司在 6月18日发布的首次情况更新中表示，该行为者访问了多个相连客户环境中的数据，但没有证据表明存储在 Klue 平台中的客户内容受到影响。\u003C\u002Fp>\n\n\u003Cp>Klue 表示，CrowdStrike 于 6月30日完成调查，并于 7月1日公布了调查结果摘要。该摘要称，没有证据表明与集成服务无关的 Klue 系统遭到访问，6月12日之后也未发现该行为者在 Klue 环境中活动。调查人员未能确定最初的 GitHub 令牌是如何被获取的。以上是已公布调查结果所涵盖的范围，不能据此认定已排除相连第三方环境中所有可能的影响。\u003C\u002Fp>\n\n\u003Ch2>哪些数据类别有证据支持？\u003C\u002Fh2>\n\u003Cp>结构化数据类别仅限于第三方集成凭据和身份验证令牌。官方摘要明确指出，后者包括 Salesforce OAuth 访问令牌和刷新令牌。这些类别并不意味着所有 Klue 客户、每个连接或存储在 Klue 平台中的内容都受到了影响。各机构后续发布的通知分别作为独立事件记录保留，不会与这一上级集成事件合并而造成重复计数。\u003C\u002Fp>\n\n\u003Cp>除轮换令牌和关闭 pods 外，Klue 还介绍了在访问控制、网络分段、机密管理、监控以及受控重新启用集成方面开展的工作。直接收到 Klue 或相连平台通知的组织，应撤销并更换相关 OAuth 令牌，并在各自的范围内审查 6月11日至12日期间的关联应用权限和访问日志。对于未收到通知的用户，已发布的资料不足以确定个人层面的影响。\u003C\u002Fp>","Klue 2026 年 OAuth 供应链数据泄露. 受影响的总数尚未披露。 已报告的数据：第三方集成凭据, 身份验证令牌。 了解影响范围、风险及防护措施。","\u002Fuploads\u002Flogo\u002Fklue_com.svg",false,{"name":54,"sector":55,"country":56,"website":10,"websiteArchiveUrl":57,"websiteStatus":58,"websiteCheckedAt":59},"Klue","Software","Canada","","active","2026-07-29T21:42:00.000Z",{"success":4,"breaches":61},[62,70,77,84],{"slug":63,"title":64,"companyName":65,"logoUrl":66,"breachDate":67,"affectedCount":68,"affectedCountStatus":69},"joomlart","JoomlArt 2018年数据泄露事件","JoomlArt","\u002Fuploads\u002Flogo\u002Fjoomlart_com.webp","2018-01-30T00:00:00.000Z",22477,"known",{"slug":71,"title":72,"companyName":73,"logoUrl":74,"breachDate":75,"affectedCount":76,"affectedCountStatus":69},"medela","Medela 数据泄露","Medela","\u002Fuploads\u002Flogo\u002Fmedela.webp","2026-09-07T00:00:00.000Z",423947,{"slug":78,"title":79,"companyName":80,"logoUrl":81,"breachDate":82,"affectedCount":83,"affectedCountStatus":69},"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":85,"title":86,"companyName":87,"logoUrl":88,"breachDate":89,"affectedCount":90,"affectedCountStatus":69},"elekta-2026-data-breach","Elekta 2026年数据泄露事件","Elekta AB","\u002Fuploads\u002Flogo\u002Felekta-2026-veri-ihlali-afc72236a8ad.webp","2026-09-01T00:00:00.000Z",129576]