IllustrationSome newly published content is awaiting English translation and is shown in Traditional Chinese.
GLOBAL DAILY / 2026-10-31
Global Cybersecurity Risk Briefing
Source facts, our analysis and protective actions for businesses
Start with the news highlights
3 analyses in this issue · 1 recent news item
Illustration
IllustrationMicrosoft 補充 Cursor 惡意 Claude Code 事件:2.1.312 亦受影響
Microsoft Security Research ↗
IllustrationAWS Private CA Connector for Kubernetes fixes issuer authorisation; check certificate types before upgrading
Amazon Web Services ↗
IllustrationGitLab removes trust in compromised certificates: update self-managed Runner and AI Gateway too
GitLab ↗Publication Times, Sources and Editorial Notes
Understand risk through evidence. Prioritise prevention, isolation and verifiable recovery, giving readers practical next steps without creating fear.
Briefing date:· Published:2026.10.31 02:15 HKT
SI assistance: yes; human review: not completed
Recent news is supplementary reading and is not counted among this issue's analyses. Source scan times and content publication times are recorded separately.
View source monitoring log ↗01 / Daily Analysis
Back to the four-story overview ↑Cursor 市集曾提供遭植入後門的 Claude Code 擴充功能 2.1.313
Published in this issue:

Facts
Sophos X-Ops 於 10 月 30 日整理事件:Cursor 在 10 月 29 日通報,惡意版本的 Anthropic Claude Code 擴充功能 2.1.313 曾於約 09:27 至 20:35 UTC 在 Cursor 擴充功能市集提供,涉及 macOS 及 Windows 套件,Cursor 估計最多 5,000 名使用者受影響。Sophos 引述分析指出,該版本會加入攻擊者控制的 SSH 金鑰、嘗試建立反向 SSH 通道與持久化,並傳送主機資料;由於程式錯誤,啟用 SSH 的步驟在大多數 macOS 及 Windows 主機會失敗。
Analysis
Our analysis:這是開發工具市集的供應鏈事件,不等同 Claude 模型或所有 Claude Code 安裝均被入侵。開發人員裝置通常能接觸程式碼、雲端憑證及部署環境;即使部分後門步驟失敗,仍須按已安裝版本及暴露時段調查,不能只靠解除安裝判定風險已清除。
Suggested Actions
- 盤點使用 Cursor 的 macOS 及 Windows 主機,確認是否在 10 月 29 日暴露時段安裝過 Claude Code 2.1.313。
- 發現相關版本時先隔離並保存證據,檢查未授權 SSH 金鑰、持久化項目及異常通道程序;只解除安裝擴充功能並不足夠。
- 輪換該主機可存取的程式碼平台、雲端及部署憑證;如無法確認清除完整,按事件程序重建裝置。
Scope:全球使用 Cursor 及相關 Claude Code 擴充功能的開發團隊 · Supply chain security
Event date:2026-10-29
Source
- Sophos X-Ops · Malicious Claude Code extension distributed through Cursor marketplace · 來源發布 2026-10-30 · 核實時間 2026.10.31 02:15 HKT
02 / Daily Analysis
Back to the four-story overview ↑Microsoft 補充 Cursor 惡意 Claude Code 事件:2.1.312 亦受影響
Published in this issue:

Facts
Microsoft Security Research 於 2026 年 10 月 30 日公布程式碼分析,確認 Cursor 擴充功能市集中遭竄改的 anthropic.claude-code 版本包括 2.1.312 及 2.1.313,暴露時段約為 10 月 29 日 02:27 至 13:35 PDT。Microsoft 表示,相關惡意套件未曾由 Microsoft Visual Studio Marketplace 或 npm 的 @anthropic-ai/claude-code 發布;Anthropic 亦向 Microsoft 確認其系統未被攻陷,現有證據顯示事件局限於 Cursor 市集。分析亦指出,載入器會嘗試加入 SSH 金鑰、建立反向 SSH 通道及跨平台持久化;即使通道失敗,仍可能留下外部檔案和啟動項目。
Analysis
Our analysis:這項更新擴大了企業需要盤點的版本範圍,亦釐清供應鏈邊界。事件不代表 Microsoft 市集、npm 套件或 Anthropic 系統整體遭入侵,但只移除或更新擴充功能不足以證明主機已清潔,因為持久化資料可能寫在擴充功能目錄之外。
Suggested Actions
- 把 Cursor 市集安裝紀錄的核對範圍擴展至 anthropic.claude-code 2.1.312 及 2.1.313,並保留受影響時段的端點及網絡證據。
- 發現相關版本或載入活動時先隔離裝置,再按 Microsoft 與 Cursor 公告核對未授權 SSH 金鑰、啟動項目及異常通道程序;不要只解除安裝擴充功能。
- 如調查顯示憑證、工作階段或主機信任可能受影響,從已知乾淨裝置輪換憑證、撤銷工作階段,並按事件程序評估重建。
Scope:全球使用 Cursor 及相關 Claude Code 擴充功能的開發團隊 · Supply chain security
Event date:2026-10-29
實質更新:Microsoft 的原始程式碼分析把已確認的惡意 Cursor 市集版本由先前報道的 2.1.313 擴展至 2.1.312 及 2.1.313,並明確確認 Microsoft Visual Studio Marketplace、npm 套件及 Anthropic 系統不在這宗事件的受影響範圍;另補充移除擴充功能不會自動清除寫在外部的持久化資料。
Source
- Microsoft Security Research · Inside a malicious Claude Code-branded extension and its persistent SSH backdoor · 來源發布 2026-10-30 · 核實時間 2026.10.31 20:22 HKT
03 / Daily Analysis
Back to the four-story overview ↑GitLab removes trust in compromised certificates: update self-managed Runner and AI Gateway too
Published in this issue:

Facts
GitLab says CVE-2026-111943 concerns eight eMudhra intermediate certificates with compromised private keys; updates remove trust in those certificates from GitLab CE/EE. GitLab.com is already updated, as are GitLab Dedicated tenants running 19.4.3-internal0 or later. Self-managed users should check the fixed release for their branch.
Analysis
Our analysis: updating GitLab itself does not update Runner or AI Gateway. These components validate certificates separately, so teams should check each one and the independent certificate packages in build images.
Suggested Actions
- Check the GitLab CE/EE version against the official advisory and upgrade to the fixed release for your branch.
- Update self-managed GitLab Runner to 19.5.1 and rebuild CI/CD job images containing their own ca-certificates package.
- Update self-managed AI Gateway to the fixed release for its branch and verify the deployment and connections again.
Scope:全球使用自建 GitLab 的機構 · Security updates
Source
- GitLab · GitLab Patch Release and Security Update: 19.5.3, 19.4.5, 19.3.7, 19.2.10, 19.1.10, 19.0.11, 18.11.14 · 來源未列發布時間 · 核實時間 2026.10.31 06:11 HKT
This article was prepared with assistance from SI agents. Factual summaries, vendor claims and Anti-Ransomware analysis are presented separately. It provides general information and education, not professional advice for a particular environment. Completeness, timeliness, accuracy and product security are not guaranteed, nor are prevention, decryption or recovery. Check the original sources and consult qualified professionals about your environment. Inclusion does not imply certification, endorsement or partnership. Trademarks and rights to original text belong to their respective owners.
KEEP EXPLORING
Keep reading more news
Newest first. Scroll down to keep reading.
Scroll down to keep reading more news.