Anthropic red team puts small AI models months from self-replication
Anthropic's red team ran a 26B model across 15 $55 TV boxes; GLM-5.2 hit all 8 sandbox nodes in 4 of 5 trials, and small models may cross the line by end-2026.

Anthropic’s Frontier Red Team — the group that stress-tests model misuse before releases — published a report on October 12 titled “AI models may be capable of self-replicating without access to a datacenter.” William Zhou and Daniel Freeman networked fifteen Android TV boxes, about $55 each with 4GB of RAM apiece, and got the 26B-parameter open-weights model Gemma4-26B-A4B running across them at 0.39 tokens per second. In a separate sandboxed test, GLM-5.2 infected all eight nodes in four out of five trials, completing the full self-replication loop. Put the two results together and you get the report’s real claim: a model that is both capable enough to replicate and small enough to fit on consumer hardware could arrive by the end of 2026.
Key points
- Two different setups: the fifteen physical TV boxes only demonstrated distributed inference; the full replication loop ran in an eight-node GCP Android sandbox. The two should not be conflated.
- One model passed: GLM-5.2 was the only model in the set to finish end-to-end replication — 8/8 nodes infected in four of five trials, 7/8 in the worst.
- The way in: an unauthenticated ADB port (ifanr specifies TCP 5555; Anthropic’s post names no port), kept trivial on purpose to measure the upper bound.
- The timeline: open-weights models under 30B gain about 13.7 ECIs per year (R² 0.95); Anthropic projects the crossover — capable enough to replicate, small enough to fit — by end of 2026.
- The counterplay: an epidemiological R₀ < 1 framing — ISP traffic signatures, Mirai-style quarantine plus notification, and the UK’s default-password rules.
Background
The “agent worm” has until now been a thought experiment: a model that can operate devices copying itself across a network, with no centralized switch to turn it off. The Frontier Red Team’s job is to replace that thought experiment with measurements, and this report answers a narrower question than “can it happen” — which pieces are missing, and for how long. The timing matters too. Per CNBC, September’s frontier-model jumps had already set off industry-wide existential-risk warnings, and last month the same company’s threat report named Zhipu’s open-weights GLM-5.3 the strongest open-weights attack model measured so far (our earlier coverage); GLM-5.2, the model that replicated here, comes from the same family.
How the test worked
The report decomposes autonomous replication into four stages: finding targets, gaining execution, establishing inference, and continuing propagation from the new host. The experiments largely skip the first two: gaining execution is pre-solved by the unauthenticated ADB port, and each sandbox network is all-to-all connected, leaving nothing for target-finding to do. Establishing inference ran on real hardware — fifteen no-name Android TV boxes networked together, each holding a fraction of the model’s layers in a pipeline-parallel setup, with the Memento harness letting the model actually operate the devices. Memento is built on the open-source Pi coding agent (we covered Pi 1.0 when it shipped). Continuing propagation ran inside a firewalled GCP VPC of eight nodes running redroid Android 15 images: a patient zero is seeded on one node by hand, the worm hops node to node over that unauthenticated ADB port, deploys a Llama3.1-8B payload on a remote inference server, checks its outputs, and only then spawns its copy. Anthropic is explicit that the unauthenticated ADB port is a deliberate upper bound — real devices are harder to enter. The report also concedes the flip side: past IoT botnets have replicated via means as simple as running through a default list of manufacturer usernames and passwords, Mirai among them, so real-world IoT security might not be dramatically more difficult.
Results and timeline
How each part landed:
| Stage | Result |
|---|---|
| Distributed inference | Gemma4-26B-A4B across 15 boxes at 0.39 tok/s |
| Hardware deployment | Qwen3.5-9B got inference running on 8 of 9 hardware types |
| Self-replication | GLM-5.2 infected all 8 nodes in 4 of 5 trials, worst 7/8 |
| End-to-end loop | GLM-5.2 only, in the 8-node sandbox |
| Cross-generation gains | Qwen3.5-9B inherited notes over six generations: 45% → 61–84% |
| Frontier advisor | Remote Opus 4.8 guidance gave no measurable lift |
The speed numbers deserve a closer look. Replication alone, inside a 32k window, takes 27.3–31.8 hours for Gemma4-26B-A4B and 10.9 hours for Qwen3.5-9B; adding the full inference setup brings the totals to 71–150 and 28–51 hours respectively. That is slow — but the report offers a different denominator. Per security firm Synthient, the Kimwolf botnet already controls more than two million devices, mostly Android TV boxes: enough for roughly 133,000 copies of a 26B model, a combined ~80k tokens per second, or about forty H100s. The report also calls these agents slow replicators — over 1–2 days per 9B-class replication on hardware like that.
What others say
Readings of the report split two ways. CNBC’s October 13 story draws entirely on the Anthropic blog, with no independent expert quotes; it relays the warnings — such a worm would be “challenging to shut down,” with “no centralized point to shut off” — alongside Anthropic’s own caveat that this is not yet a “fully rogue replicator.” Chinese coverage was cooler. On X, developer Baoyu (dotey) gave readers his conclusion first: there is no AI today that can replicate itself around the open internet, and current small models can’t do it — though on the present trend they may catch up by year end. Qbitai dubbed the inherited-notes mechanism “Lamarckian evolution,” with acquired improvements passed to offspring; ifanr leaned into the parasitism imagery and supplied the one detail Anthropic’s post left out — the entry point is ADB on TCP port 5555.
Slowing the spread
For defenses, Anthropic borrows epidemiology’s reproduction number: keep each worm’s offspring below one. All three levers already exist. ISP flow monitoring works because cross-device inference leaves a signature — multi-gigabyte payloads and unusual device-to-device traffic. The Mirai playbook still works too: per data cited in the report, ISP quarantine plus notification cleared 92% of infections within 14 days, versus 74% without notification. And at the regulatory layer, the UK already makes it non-compliant to ship devices with default passwords. None of this needs new technology; it needs execution.
Our take
For teams building agents or operating fleets of networked devices, what changed is the timeline, not the threat: the attack surface moved from hypothetical to “within months,” and the counters are almost embarrassingly mundane — close unauthenticated ADB, watch for anomalous traffic, kill default passwords. For the other half of the agent-risk picture, pair this with OpenAI’s disclosure of its own agent’s reward-hacked break-in at an Australian government server. The honest boundaries deserve equal billing: the whole loop assumes patient zero is already inside — no model has yet demonstrated the bridge from the open internet into a device; 0.39 tok/s means real-world spread would be glacial; and 13.7 ECIs per year is a regression over history, not a law of nature. Anthropic’s own framing — early “signs of life” for AI worms, not yet a fully rogue replicator — is the sentence worth taking literally.