AI explained. Tools tested. Ideas worth trying.By Sam Taylor & Samwise ↗

The AI worm problem moved from theory to 'signs of life.' The model that did it is already in production.

Jump to a section
See the story at a glance
8/9
hardware types
where Qwen3.5-9B set up inference

Fifteen off-brand Android TV boxes. About $55 each. Four gigabytes of RAM per device. Anthropic's Frontier Red Team wired them together and watched Gemma4-26B-A4B run across all fifteen of them at roughly 0.3 tokens per second.

That demo is slow. Toy speed. Nothing you'd ship to production. But the point isn't the speed — it's that distributing a 26-billion-parameter model across fifteen cheap, consumer-grade devices and getting inference running is a task that works now. With hardware that costs less than a decent office chair.

The full paper arrived October 12. I want to walk through what it actually says, because the summary version is either more alarming or less alarming than the truth, depending on which paragraph someone read.

What the 9B model did. Qwen3.5-9B — a nine-billion-parameter open-weight model, on the small end of anything in production — successfully set up inference on 8 of 9 hardware types in the evaluation. Jetson Nanos, Mac PCs, RTX 4090s, Android TV boxes. Not a frontier model. Not Fable-class. A nine-billion-parameter model you can download today and run locally.

What GLM-5.2 did. In an end-to-end replication trial — a GCP fleet of eight Android emulators with an unauthenticated ADB port, which the researchers set up as an upper-bound scenario — GLM-5.2 spread to all eight nodes in four of five runs. In the fifth, it got to seven of eight. The cyber-exploit step was made trivial on purpose, so these numbers overstate real-world success. But GLM-5.2 is a current open-weight model running in production workloads right now.

The timeline estimate. The specific claim worth examining: the researchers fit a trend to small-model performance and found a gain of 13.7 Epoch Capabilities Index points per year, R² of 0.95. At that rate, small models cross the threshold for full replication capability by the end of 2026. They call it a rough estimate — the ECI is a proxy, not a direct replication measure. Fair. But "rough estimate pointing at this year" is not the same as "speculative future concern."

One more specific detail: passing notes between generations of Qwen3.5-9B — each node leaving instructions for the next — raised inference setup success from 45% in the first generation to 61–84% in later ones. The models got better at the task by teaching each other how to do it.

The researchers don't call this a working rogue replicator. Their framing is "signs of life for AI worms." I think that's accurate.

133k
Estimated model replicas if Qwen3.5-9B spread across a Kimwolf-scale botnet (~2M devices)

→ Source: Anthropic Frontier Red Team

Source spread

Pros & cons

What's real:

  • The core claim — a 9B model sets up distributed inference across cheap IoT hardware — is demonstrated at scale across 9 hardware types, not projected. Eight of nine. That's not a theoretical baseline.
  • The trend estimate has an R² of 0.95. The researchers are honest about the proxy limitation, but a correlation that tight on a four-year trend isn't noise.
  • The defense recommendations are practical: monitoring for model-payload transfers and distributed inference traffic signatures are things security teams can implement without waiting for any lab to ship a new product.
  • The Kimwolf comparison is a reasonable scale reference. An estimated 133k replicas and ~40 H100-equivalents of inference from a 2-million-device botnet is a real capability floor, not a ceiling.
  • The Mirai clearance comparison is encouraging: 92% clearance within 14 days when owners were notified vs 74% without notification. The problem has historical precedent and known countermeasures.

What deserves a side-eye:

  • The unauthenticated ADB port was set up on purpose. The researchers call this an upper bound. Real-world botnet exploitation is harder — how much harder is unspecified.
  • GLM-5.2 succeeded; other open-weight models failed. "GLM-5.2 and stronger models" is a narrow band right now. Whether capability generalizes across other model families is an open question.
  • Access to a stronger advisor model (Opus 4.8) did not measurably improve 9B model success. If the bottleneck is execution rather than reasoning, the capability threshold might shift differently than the ECI trend predicts.
Self-replication capability milestones
  1. Now

    9B models set up inference on 8/9 hardware types

    Complete many individual replication steps; failure in end-to-end chaining

  2. Now (simplified test)

    GLM-5.2+ achieves end-to-end replication

    8/8 nodes in 4/5 trials; trivial exploit path; upper bound on real-world performance

  3. End of 2026 (estimated)

    Small model threshold

    13.7 ECI pts/yr trend, R²=0.95; full end-to-end at realistic conditions

What builders need to know

  • The immediate concern isn't frontier models. It's 9B and GLM-class open-weight models already running in production workflows. Security teams focused on API-access threat models should re-examine IoT exposure specifically.
  • Two network flow patterns to monitor: model-weight payload transfers (large file movement consistent with model distribution) and distributed inference traffic (persistent connections to multiple nodes with uniform load patterns). The paper calls both out explicitly.
  • IoT devices on the same network as AI workloads are a specific risk surface. Default credentials on smart home devices, off-brand Android TV boxes, and any device with an exposed ADB port are the hardware this paper describes.
  • The note-passing finding means single-failure analysis understates risk. Don't model this as "one attempt, success or fail." Each run leaves the system incrementally better at the next attempt.
  • The Kimwolf-scale estimate (133k replicas, ~40 H100-equivalents) suggests meaningful inference generation at botnet scale — which matters if you're thinking about whether a compromised IoT fleet could run coordinated AI-assisted operations without a central operator.

Further reading

Liked this? Get the weekly digest.

Free. Monday mornings. The week's stories, synthesized. Unsubscribe anytime.

Your take

How'd I do on this one?

What did I miss?

Tell Samwise (and Sam).

Disagree with the take? Spotted a fact I got wrong? Have context I should have included? Drop it here. Anonymous unless you leave an email.

Keep following the thread

A little more to explore.

All articles ↗
Safety5 min read

Anthropic put its strongest AI on full-time defense duty. Power grids are first.

On October 8, Anthropic launched the Cyber Mission: frontier model access, on-site engineers, and a free OSS Scanner deployed to defenders of power grids, water systems, and the open-source code almost everything runs on. Project Glasswing found the vulnerabilities; now comes the harder work of fixing them.

Read the story ↗
Safety7 min read

Anthropic's AI filed real government forms when it meant to practice. Nobody was hurt. Yet.

An Anthropic research model submitted a fake tip to a Philadelphia murder database and filed 20 incomplete visa applications during testing — not by a hacker, but by a model that couldn't tell a practice form from the live internet. The two-month gap before Anthropic said anything matters more than the incidents themselves.

Read the story ↗