FR
live
AI

Anthropic warns autonomous AI agents could spread like worms across IoT devices

On October 13, 2026, Anthropic warned, via the Financial Times, that increasingly capable autonomous AI agents could behave like self-replicating worms on poorly secured connected devices. This is not a breach disclosure but a shift in the threat model that security teams should internalize now.

A long fallen line of black dominoes on a dark table, the single leading domino glowing amber.

October 13, 2026. The Financial Times reports that Anthropic, the maker of Claude, warns that increasingly capable autonomous AI agents could eventually behave like self-replicating computer worms, spreading across poorly secured connected devices — televisions, thermostats, cameras, appliances. October 13, 2026. The lab compares the possibility to digital organisms moving through interconnected environments. August 2026. A preprint from Anthropic and EPFL had already shown payloads hopping from one agent to another through prompt files. Why it matters: the news is not “an AI worm is on the loose” but that adaptive malware — code that changes its behavior as it explores a network — has become a credible scenario in the eyes of a leading lab.

Malware that adapts instead of executing a script

The difference between a classic worm and the scenario Anthropic describes comes down to one word: adaptation. Traditional malware follows relatively fixed instructions — a list of vulnerabilities to try, steps coded in advance. An autonomous AI agent, by contrast, could reconnoiter its environment, identify weaknesses, and adjust its trajectory as it moves to new devices.

That shift from “code that executes” to “code that decides” changes the nature of defense. Detection built on signatures or indicators of compromise assumes the attacker behaves reproducibly. Against an adversary that re-evaluates its strategy at every step, those signals become fragile.

One point of framing matters. Anthropic is describing a potential future threat, not announcing an active campaign. The lab is not claiming autonomous AI worms are already spreading through living rooms. But the fact that it says so publicly — and precisely enough to be picked up by a major financial daily — signals the topic has moved from science fiction to risk analysis.

The ideal terrain: unpatched IoT

The scenario becomes worrying precisely because the connected-device fleet is, structurally, the most poorly defended there is. Many devices — cheap cameras, routers, appliances — keep running years after their software support ends. The vendor no longer ships patches, the user would not apply them anyway, and the device stays online around the clock.

AI changes the equation because it can automate what previously required a skilled human operator: identifying devices, enumerating their weaknesses, adapting to the quirks of each environment. An AI worm does not need one universal vulnerability; it only needs enough, one per target.

Add to that a formidable property of distributed threats: a network of compromised devices with no central command server is hard to take down. There is no single point to “switch off.” Every infected device is both victim and relay.

What it changes for a security team

The most useful signal in the warning is not technical but strategic. It is a reminder that the boundary between the corporate network and the home network has become porous — a connected TV on the same network as a workstation is an entry point, not furniture.

The measures Anthropic cites are, from that angle, strikingly sober: device security, software maintenance, network isolation, and limits on what automated systems are allowed to do. Nothing spectacular — which is exactly the point. Against an adaptive threat, the answer is not a miracle tool but architectural hygiene: segmenting IoT and OT from the rest of the network, inventorying connected devices, applying patches while they exist, and retiring the ones that no longer receive any.

The point about limits placed on agents may be the most novel. If autonomous agents are going to touch our systems, the defense must include guardrails on their permissions — what they can read, write, execute, and pivot toward. That is the principle of least privilege, extended into the world of agents.

Verdict

If you manage a corporate network, treat this warning as one more dated argument for two projects you may be deferring: segmenting IoT and OT, and building a real inventory of the connected devices touching your network, including the ones people plug in without telling you. If you run AI agents internally, add an explicit lock on their execution and lateral-movement permissions now, rather than waiting for an incident to force it. If you self-host as an individual: your router, cameras, and connected appliances are your attack surface — isolate them on a dedicated VLAN and turn off what you do not use. The threat described is not here today, but the terrain that would make it dangerous already exists.

References

The cyber brief, every Tuesday

The flaws that matter and the patches to apply, in a ten-minute read.

No spam. One-click unsubscribe.
read next

On the same topic

Anthropic says it cut distillation theft from Claude by 90 to 99 percent

On October 12, 2026, Anthropic published a research post detailing three defenses against distillation: preserved thinking, a two-stage classifier, and mass account bans. Harvested data is claimed to have fallen by 90 to 99 percent, but the figures are vendor measurements, not an independent audit.

Meta launches Muse Wonder, its first frontier model, and bets on memory over benchmarks

On October 12, 2026, Meta’s Superintelligence Lab shipped Muse Wonder and Muse Wonder Full, its first frontier models, positioned around “active memory” and agentic work rather than raw benchmark leadership. The launch closes Meta’s lightweight-model era and raises a governance question: what do you do with an agent that remembers your messages, calendar, and documents?

← Back to the feed

Type at least two characters.

↑ ↓ navigate ↵ open esc dismiss