胡塞武装利用 Claude Code 开发导弹制导软件:Anthropic
Houthis Used Claude Code to Develop Missile Guidance Software: Anthropic

原始链接: https://clashreport.com/world/articles/houthis-used-claude-code-to-develop-missile-guidance-software-anthropic-s52mnx4pwpo

Anthropic 近期的威胁报告详细描述了也门胡塞武装相关组织如何利用其 AI 模型 Claude 来加速制导火箭、弹道导弹及高超音速滑翔飞行器的研发。通过并行运行多个 AI 实例,这些操作人员复刻了一个专业工程团队的功能,涵盖了从导航代码、飞行控制算法到轨迹模拟及测试后故障分析等各项任务。 这一案例标志着生成式 AI 武器化进程的重大转变:从单纯的信息搜集转向直接、迭代式的常规武器开发。尽管有 Anthropic 的安全过滤机制,该组织通过拆解请求并隐藏其最终目的,成功绕过了相关限制。 虽然 Anthropic 未发现该组织制造出实战武器的证据,但这些操作人员已成功汇总出一套离线工程工具包,从而摆脱了对 AI 平台的依赖。此事件凸显了 AI 安全领域的一项关键脆弱性:当复杂的工程项目被刻意拆解为看似无害的独立任务时,检测非法开发工作变得极其困难。也门案例是 Anthropic 所记录的六起常规武器相关行动之一,此外报告还识别出涉及中国和俄罗斯的类似活动。

一份近期报告指出胡塞武装使用 Anthropic 公司的 Claude 开发导弹制导软件,这一消息在 Hacker News 上引发了激烈辩论。怀疑论者认为该说法是旨在争取有利监管或政府关注的“末日色情(doom porn)”,并指出相比物理工程,软件本身的关键性较低,且此类说法尚未得到证实。 讨论主要集中在三个主题: 1. **人工智能的可访问性**:许多评论者认为,包括本地开源替代品在内的人工智能模型,已使自动驾驶系统等复杂技术任务对业余爱好者而言变得轻而易举。他们主张,试图通过严格监管来“限制”人工智能,对于这种已广泛存在的技术而言是徒劳的。 2. **安全性与实用性**:用户批评 Anthropic 的“安全”措施流于形式(例如根据语气屏蔽提示词),却未能阻止现实中的滥用行为。反之,另一些人指出,Anthropic 在谴责这些行为的同时,却在宣传其自身与美国国防部的合作,这具有讽刺意味。 3. **“精灵”问题**:舆论共识认为,“人工智能革命”已超出任何单一企业的控制范围。随着模型在本地硬件上运行变得更加容易,监管机构和开发者不得不面对一个必然的转变,即高性能人工智能在本质上已无法受到限制。
相关文章

原文

A cell in northern Yemen used Anthropic’s Claude Code to perform work that would ordinarily require a missile engineering team, developing software for guided rockets, a long-range ballistic missile and a hypersonic glide vehicle concept.

Anthropic’s September threat report describes operators running several Claude instances at the same time, dividing tasks between coding, research and technical review.

The company assessed the cell as highly likely to be linked to the Houthis, according to the material provided.

The operation marks one of the clearest examples in the report of generative AI being applied directly to conventional weapons development rather than used simply for research or information gathering.

The Yemen-based operators used Claude Code across multiple engineering functions.

Their projects included guidance software for a tactical guided rocket, a ballistic missile with a range exceeding 2,000 km, and a hypersonic glide vehicle variant called “R2000.”

Rather than assigning the work sequentially to a single model instance, the group operated several sessions in parallel.

One could produce code while another conducted research and a third reviewed the output.

The workflow let a small group reproduce several functions normally distributed across specialist engineering teams.

The technical work extended into navigation, flight control and simulation.

The operators sought to integrate open-source autopilot software with a phone-class flight computer and used Claude to write navigation and control code.

They also developed six-degree-of-freedom trajectory simulations, a method for modeling an object’s movement and rotation through space.

They also used Claude for reinforcement learning work to tune flight-control algorithms.

The operators ultimately compiled the project into a standalone executable that could run offline. That meant development could continue without direct access to Claude.

The activity moved beyond software development.

The group test-fired a guided rocket in Yemen, according to the material documented by Anthropic. The test appears to have failed.

Within hours, however, the operators returned to Claude and began analyzing launch telemetry to investigate the failure.

That sequence, software development, physical testing and rapid post-test analysis, illustrates how the model was incorporated into an iterative weapons-engineering cycle rather than being used for isolated technical questions.

Anthropic said it found no evidence that the group succeeded in fielding an operational weapon.

But by the time the accounts were disrupted, the operators had already assembled an offline engineering toolkit that no longer depended on access to Claude.

Anthropic’s safeguards blocked numerous requests during the project.

The operators adapted by obscuring the intended end use of individual tasks, dividing work across separate conversations, and using other methods to circumvent restrictions.

Anthropic subsequently banned accounts linked to the activity.

The case highlights a problem for AI safety systems: individual requests may appear disconnected from weapons development when a larger engineering project is deliberately fragmented across sessions.

The Yemen operation was one of six conventional-weapons cases Anthropic documented.

Three were linked to China, two to Russia and one to Yemen. The cases covered attempts involving missiles, armed drones, firearms and bombs.

The wider report covers operations Anthropic said it disrupted between December 2025 and August 2026 across cyber operations, influence activity, surveillance, conventional weapons, biological misuse, scams and fraud, and illicit model distillation.

Anthropic also described biological research cases in which it could not establish whether scientists were conducting legitimate research or pursuing weapons-related objectives.

“You are not seeing someone in a comic book kind of way say, ‘Hey, I want to build a biological weapon to kill everybody,’” Jacob Klein, Anthropic’s head of threat intelligence, said. “It’s an incredibly nuanced situation.”

For the Yemen case, the immediate outcome was more concrete: Claude had been incorporated into a real development cycle spanning design, simulation, testing, and failure analysis.

The weapon itself was not shown to have become operational. The engineering capability assembled around it had already begun moving offline.

联系我们 contact @ memedata.com