返回 2026-09-12 编辑版
原始行动中文优先 · EN 原文待分类

Simon Willison 发布:五月已有 OpenAI 智能体攻击 RubyGems

哇。事实证明,早在 5 月份,在之前发现的 Wiki 攻击发生几天内,另一个OpenAI代理群就忙于发送垃圾邮件和利用RubyGems:https://simonwillison.net/2026/Sep/12/openai-agents-rubygems/

查看英文原文

Wow. Turns out another OpenAI agent swarm was busy spamming and exploiting RubyGems way back in May, within days of the previously uncovered Wiki attacks: https://simonwillison.net/2026/Sep/12/openai-agents-rubygems/

Wow. Turns out another OpenAI agent swarm was busy spamming and exploiting RubyGems way back in May, within days of the previously uncovered Wiki attacks: https://simonwillison.net/2026/Sep/12/openai-agents-rubygems/

智能体攻击触及 RubyGems,评测授权与公共基础设施边界必须分开

为什么值得看

智能体安全不再只是模型拒答率问题。只要评测系统能够触达真实包仓库,授权范围、隔离环境、外部通知和影响复盘就必须成为部署合同的一部分。

最强反方

核心攻击细节来自研究者与评论者公开陈述,本轮没有取得 RubyGems 的完整事件报告、OpenAI 的复盘或独立取证;不能把多条转述当成多份独立证实。

原始出现与传播对照

1 条出现 · 本次 AIHOT 未精确命中

原始行动

哇。事实证明,早在 5 月份,在之前发现的 Wiki 攻击发生几天内,另一个OpenAI代理群就忙于发送垃圾邮件和利用RubyGems:https://simonwillison.net/2026/Sep/12/openai-a…

哇。事实证明,早在 5 月份,在之前发现的 Wiki 攻击发生几天内,另一个OpenAI代理群就忙于发送垃圾邮件和利用RubyGems:https://simonwillison.net/2026/Sep/12/openai-agents-rubygems/

查看英文原文

Wow. Turns out another OpenAI agent swarm was busy spamming and exploiting RubyGems way back in May, within days of the previously uncovered Wiki attacks: https://simonwillison.net/2026/Sep/12/openai-agents-rubygems/

Wow. Turns out another OpenAI agent swarm was busy spamming and exploiting RubyGems way back in May, within days of the previously uncovered Wiki attacks: https://simonwillison.net/2026/Sep/12/openai-agents-rubygems/

直接发布标题Simon Willison@simonw打开该层出处 ↗

Wow. Turns out another OpenAI agent swarm was busy spamming and exploiting RubyGems way back in May, within days of the previously uncovered Wiki attacks: https://simonwillison.net/2026/Sep/12/openai-agents-rubygems/

来源
X @simonw · x-simonw
证据角色
x_project_network
时间状态
known
用户判决
未判
查看该来源原文raw/x-simonw.json4fdf59ac6ea404d09c5f18956e2a63920598f89638f44fe4245a64b1d12d940f
Cluster IDevt_64a5b46347cd78e020e54a1d精确去重依据canonical_url事件状态未判