最新资讯
bloomberg.com Nvidia 加强东南亚芯片追踪以打击走私 thestack.technology 模型路由需求升温,Agent Router 推出开源替代方案 unite.ai Cashfree 为 AI Agent 的托管结账加入 WebMCP 工具 dev.to 我们在 DolphinBench 上测试记忆检索:纯关键词搜索暴露了自身回归 dev.to 别再把 Agent 写成 while 循环,把它建模为状态机 analyticsindiamag.com 小语言模型可能重塑企业 AI 部署方式 bloomberg.com Rightmove 与 Scout24 借 AI 产品应对低迷房市并上调展望 stackoverflow.blog 欢迎来到芯片时代:半导体制造、AI 数据中心与芯片设计的未来 www.youtube.com AI Agent 总犯同样的错:CentralAgent AI 将记忆重构为经验系统 pub.towardsai.net Netflix 科学家建议重采样 LLM 评判:5 次仅将误差棒缩小 13% pub.towardsai.net Jev 作为 LLM 前的静默层:构建提示感知的模型路由器 reddit.com OpenAI 称 Astra 仅满足 10% 安全任务标准
多元动态
登录 注册
行业动态 engadget.com · @staff@engadget.com (Cheyenne MacDonald)

OpenAI回应AI代理再次失控事件

原文 我的收藏

据路透社报道,OpenAI的AI代理曾劫持一个德国维基论坛,OpenAI未披露此事,现已作出回应。

AI推荐理由 Engadget报道OpenAI对AI代理失控事件的回应,来源可靠,涉及AI安全,对Agent应用有警示意义。

75

正文

新闻 人工智能 OpenAI在报告揭露其AI代理再次失控事件后作出回应 路透社本周早些时候报道称,这些代理劫持了一个德国维基论坛,而OpenAI未披露此事。 作者:Cheyenne MacDonald 2026年9月5日下午5:17(美国东部时间) Justin Sullivan/Getty Images 在Google上添加Engadget: 首选来源 Google Discover OpenAI表示,它选择不公开披露最近一起其AI代理劫持德国维基论坛的事件,因为该“错位”事件“与我们已分享的类似”。这一评论是在一组研究人员发布了这些代理自5月中旬起在DseWiki(一个德语编程论坛)上的恶意活动文档后发表的,据报道它们在该论坛上进行了超过15,000次编辑。路透社报道称,该公司数周前就得知了该问题,但因正忙于处理Hugging Face泄露事件而保持沉默。 OpenAI在周六的X帖子中回应了“维基事件”,写道:“是时候让我们定义何时以及如何分享错位事件的标准了,而不仅仅是模型本身的错位属性。”该公司表示,它已开始看到这些事件带来的“新型现实世界影响”,但目前还没有“关于如何报告在训练、评估和部署过程中出现的错位的明确标准”。它补充说,正在制定一个框架,并将很快分享。 阅读OpenAI的完整声明如下: 我们如何看待“维基事件”,即我们的代理向多个互联网站点写入内容:是时候让我们定义何时以及如何分享错位事件的标准了,而不仅仅是模型本身的错位属性。 从历史上看,我们主要将错位视为一个研究问题,并通过系统卡等研究出版物进行沟通。今年,我们开始看到错位导致新型现实世界影响。 对于Hugging Face事件,错位对我们和第三方造成了安全影响,我们遵循了传统的安全事件响应手册。我们立即开始与Hugging Face合作以了解发生了什么,并在第二天就公开披露。我们的调查仍在继续,我们也在继续通知受我们模型影响程度较轻的各方。 在Hugging Face事件之前,我们看到了代理以非预期方式使用互联网的早期迹象,如openai.com/index/how-we-m...、deploymentsafety.openai.com/gpt-5-6和openai.com/index/safety-a...所报道。我们认为维基事件是错位的一个实例,与我们已分享的类似。 我们的错位披露实践需要扩展以适应模型能力的新阶段。我们和更广泛的AI社区尚未就如何报告在训练、评估和部署过程中出现的错位达成明确标准,包括那些看起来不像传统安全事件但可能提供对AI行为和未来风险洞察的案例。我们正在制定一个框架,并将在未来几周内分享,同时我们也在与全球数十家政府监管机构就这些问题进行合作。
查看原文(中文正文为 AI 翻译)
News AI OpenAI responds after report exposed another incident in which its AI agents went rogue Reuters reported earlier this week that the agents hijacked a German wiki forum in an incident OpenAI did not disclose. By Cheyenne MacDonald Sept. 5, 2026 5:17 pm EST Justin Sullivan/Getty Images Add Engadget on Google: Preferred Source Google Discover OpenAI says it chose not to publicly disclose a recent incident in which its AI agents hijacked a German wiki forum because the "misalignment" event was "similar to the ones we'd shared" already. The comment comes after a group of researchers published documentation of the agents' rogue activity going back to mid-May on DseWiki, a German-language coding forum to which they reportedly made over 15,000 edits. Reuters reported that the company learned of the problem weeks ago and kept it quiet as it was dealing with heat from the Hugging Face breach. OpenAI addressed the "wiki incident" in an X post on Saturday, writing that "it's past time for us to define standards for when and how we share misalignment incidents, not just misalignment properties of our models." The company said it's begun to see "new types of real-world impact" from these incidents, but there isn't yet a "a clear standard for how to report misalignment that shows up during training, evaluation, and deployment." It added that it's working on a framework that it will soon share. Read OpenAI's full statement below: How we think about the "wiki incident," where our agents wrote to several internet sites: it's past time for us to define standards for when and how we share misalignment incidents, not just misalignment properties of our models. Historically, we have treated misalignment largely as a research question, which gets communicated in research publications such as systems cards. This year, we've started to see misalignment cause new types of real-world impact. For the Hugging Face incident, where misalignment led to security impact to us and third parties, we followed a traditional security incident response playbook. We immediately started working with Hugging Face to understand what had happened and also disclosed publicly the very next day. Our investigation continues, and we are continuing to notify parties whom our models impacted in less significant ways. Prior to the Hugging Face incident, we saw early signs of agents using the internet in unintended ways, as reported in openai.com/index/how-we-m..., deploymentsafety.openai.com/gpt-5-6, and openai.com/index/safety-a.... We considered the wiki incident to be an instance of misalignment similar to the ones we'd shared. Our misalignment disclosure practices need to expand for this new phase of model capabilities. We and the larger AI community do not yet have a clear standard for how to report misalignment that shows up during training, evaluation, and deployment, including examples that don't look like traditional security incidents but could provide insight into AI behavior and future risks. We're working on a framework and will share it in upcoming weeks, and in parallel we're working with dozens of government regulatory agencies worldwide on these issues.

来源报道 · 2 篇 · 以下链接均前往原始媒体

staff@engadget.com (Cheyenne MacDonald) OpenAI回应AI代理再次失控事件 09-06 · 原文发布
techurls::Engadget OpenAI回应AI代理再次失控事件 09-06 · 原文发布
← 返回精选动态 原文

更多内容