Skip to content
ISSUE 001·LIVE·23:06 IL
← Journal/2026-10-13·6 min·anthropic

Anthropic Says Small AI Models May Soon Self-Replicate on IoT Devices. What the Evidence Shows, and What It Does Not

Anthropic's October 12 research suggests small open-weight models could be months from replicating across cheap IoT devices. A careful read of the claims, the limits of its experiments, and the defensive measures it lists.

By Harel Asaf·AI Builder·Tel Aviv

On October 12, Anthropic published research with a blunt headline: AI models may be capable of self-replicating without access to a datacenter.

It is a security forecast, not an incident report. Nothing in it says an AI worm exists today. This article covers what the post claims, how it tested those claims, where the authors say the limits are, and the defensive points it lists. All claims come from Anthropic's post. I did not reproduce any experiment, and I am deliberately not summarizing operational detail.

The main claim

The authors write that small AI models "may be months away" from being capable enough to self-replicate on commercial IoT devices, such as smart ovens and off-brand Android TV boxes. They say such a replicator would be hard to shut down because there is no central point to turn off, though it may be slow, with a doubling time of days.

Two supporting statements from the post:

  • Models of 30B parameters and under can already complete many individual replication steps, but make mistakes when composing them end to end.
  • In its simplified evaluations, GLM-5.2 and stronger models can replicate end to end. If small models keep improving at their historical rate, the authors say they would match that level by the end of this year.

What they tested

Anthropic splits replication into four stages: finding targets, gaining execution, setting up inference, and continuing from the new host. It says it largely set aside the exploit stages, because earlier papers already show small models can do cyber exploits with the right tools. It focuses on setting up inference on unfamiliar hardware, which it calls less studied.

Results it reports:

  • A 9B model got inference running on 8 of the 9 hardware types tested.
  • It ran Gemma4-26B-A4B across 15 inexpensive Android TV boxes, about $55 each, at 0.39 tokens per second.
  • In a contained fleet of 8 cloud nodes emulating Android, only GLM-5.2 among the open-weight models tested replicated end to end. It reached 8 of 8 nodes in 4 of 5 trials and 7 of 8 in one.
  • In a test where each generation inherited the notes of the previous one, setup success for Qwen3.5-9B rose from 45% in the first generation to between 61% and 84% in later ones.
  • Giving a small model access to a stronger advisor model did not measurably help.

The limits the authors state

These matter as much as the headline:

  • The cyber part of the evaluation was kept trivial, with no authentication on the access port. The authors call the result an upper bound on real-world success.
  • Today, the capability needed to replicate and the small size needed to fit on cheap devices do not overlap. The "months away" claim rests on a trend line, a general capability index used as a proxy for replication ability. The authors call it a rough estimate.
  • Their speed estimate, drawn from a past botnet of over two million devices, comes to roughly 40 H100s' worth of inference at most, with replication taking days. They describe it as rough and anchored on one class of hardware.
  • They did not test whether such a worm could act intelligently against defenders.

Defense, as the post describes it

The authors frame defense as pushing the reproduction rate below 1 so the replicator dies out. Points they make:

  • A replicator at scale would leave network signatures, such as large model downloads and sustained device-to-device traffic, visible to ISP monitoring.
  • Decoy devices could help collect a replicator's code once found.
  • They cite the earlier Mirai botnet, where ISP quarantine and notification cleared 92% of infections within 14 days, against 74% without notification, and expect similar steps to help here.

I read only part of the mitigation section closely, so see the post for the full list.

What it means for builders

My own takeaways, not Anthropic's:

1. Device hygiene is the practical lever. The scenario depends on weak IoT security, such as default credentials or open ports. Changing defaults and closing unused services still matters.

2. Know what your network normally does. If you run a fleet of devices, unusual large transfers between them are worth an alert.

3. Treat it as a forecast. The post shows a plausible path and trend, not a deployed threat.

What I would not conclude

Do not read this as proof that AI worms are spreading. Do not read it as certain either: the timeline is a projection from a proxy metric.

And do not treat this as a reason to distrust open-weight models in general. The post is about misuse risk on poorly secured hardware.

Frequently asked questions

What did Anthropic publish?

A research post from October 12, 2026 on whether small AI models could self-replicate across IoT devices.

Is there an AI worm spreading now?

The post does not say so. It is a forecast based on experiments.

What is the timeline claim?

That small models could match the capability of GLM-5.2, its replication threshold, by the end of 2026 if they improve at their historical rate.

What did the experiments show?

Small models can set up inference on many hardware types, and one open-weight model replicated across a contained test fleet.

How realistic were the tests?

Simplified. The authors kept the exploit step trivial and call results an upper bound.

How could it be defended against?

Network monitoring, decoy devices, and ISP quarantine and notification, per the post.

What should I do?

Secure IoT devices, change defaults, and monitor for unusual traffic. These are my suggestions.

Sources

Related reading

The build log

Follow the work.

New essays and prototypes, in your feed reader. Email subscriptions are paused while I connect a working delivery service. No email is collected here.

Follow via RSS