The most important result in Anthropic's October 12 replication research is a separation, not a breakthrough into household networks. One experiment demonstrated adaptable inference installation. Another demonstrated propagation directed by a large, externally hosted model. Neither showed a compact AI worm running its own complete replication loop on real consumer devices.

William Zhou and Daniel Freeman of Anthropic's Frontier Red Team studied autonomous replication and adaptation, or ARA. Their research asks whether model weights could become part of a replicating payload, allowing software to troubleshoot unfamiliar machines rather than follow only predetermined instructions. The reported agents received an explicit objective inside controlled environments. This was not a model spontaneously escaping or deciding to infect devices.

The experiment that spread depended on an external brain

Replication requires four linked stages: discover targets, obtain execution, configure inference and propagate from the newly reached host. Anthropic's strongest end-to-end result used eight Android 15 emulators in a firewalled cloud network. Every node exposed an unauthenticated Android Debug Bridge port, an interface for maintenance commands and file transfer.

GLM-5.2 reached all eight nodes in four of five trials and seven in the remaining trial. It transferred a payload, established Llama 3.1 8B inference and continued the sequence. Yet GLM-5.2 itself ran through a separate inference server because it was too large for the Android targets. After the smaller inference service passed checks, the experiment launched another orchestrator instance.

Both qualifications are essential. Open ADB removed the need to discover a vulnerability or defeat authentication. External orchestration removed the requirement that the capable model fit on the machine it reached. This measures an upper bound under favorable access conditions, not a completed self-contained IoT attack. Tom's Hardware's account and BleepingComputer's analysis distinguish these missing pieces from the demonstrated components.

Smaller models can adapt after access

The deployment test addressed a different bottleneck. Model weights cannot do useful work without compatible runtimes, dependencies, drivers and sufficient memory. Across nine hardware types—including Apple silicon, NVIDIA, Google and AMD accelerators, and conventional server processors—Qwen3.5-9B established Llama 3.1 8B inference on eight.

That is meaningful technical adaptability. It is not evidence that Qwen discovered and compromised eight types of internet-connected device. Access was already available and the installation objective was supplied. Its contribution was working through software and hardware differences after entry.

Anthropic also distributed Gemma4-26B-A4B across 15 off-brand Android TV boxes using pipeline parallelism, assigning different model layers to different machines. Each box had 4 GB of memory, toward the top of the cited 1–4 GB range for this market. Together they generated just 0.39 tokens per second. Cheap hardware could collectively host inference, but not at cloud-assistant speed.

These results expose a capability floor and a hardware ceiling. GLM-5.2 could coordinate the simplified loop but did not fit the targets. Qwen3.5-9B and Gemma4-26B-A4B fit weaker hardware but did not reliably finish full propagation. No reported model crossed both boundaries at once.

Inherited notes are adaptation, not self-training weights

The Memento harness periodically replaced a stuck agent with a fresh instance that inherited its workspace and concise notes. That allowed another attempt to reconsider a mistaken diagnosis without throwing away useful files and earlier discoveries.

Successive Qwen3.5-9B generations retained successful and failed installation strategies. First-generation setup succeeded in 45% of runs; later generations achieved 61–84%. The mechanism was inherited operational knowledge in code, files and notes. The weights did not retrain themselves, and the result should not be described as autonomous biological-style evolution.

A seemingly simple workaround also failed. Giving Qwen3.5-9B access to Opus 4.8 produced no measurable improvement: the smaller model often did not recognize which question to ask, and unsolicited advice did not resolve that weakness. A stronger coordinator with weaker local workers remains conceivable, but it restores external infrastructure dependence and observable communication.

Slow execution creates a defensive opportunity

Measured throughput implied 28–51 hours for a Qwen3.5-9B inference-setup trajectory and 71–150 hours for Gemma4-26B-A4B. Performance also deteriorated substantially below a 32,000-token context window. Those are estimates based on the experiments, not observed durations of a real-world infection campaign.

Real devices would introduce blocked inbound connections, network address translation, incompatible kernels, limited storage and reboots. Distributed layers must exchange intermediate results in order; a disconnected or overloaded box can interrupt inference. Pipeline parallelism can ease node replacement but does not make an unstable fleet reliable.

Multi-gigabyte weight downloads, sustained device-to-device traffic, scans, package installations and repeated hardware inspection would provide detection opportunities. Slowing down to hide would also slow population growth. Greater persistence outside a data center is a possible risk, not evidence that bandwidth, memory or latency constraints disappear.

A convergence forecast is not a demonstrated deadline

Anthropic plotted notable open-weight models with at most 30 billion total parameters and found a trend of 13.7 annual points on the Epoch Capabilities Index. Extrapolation put a small model near GLM-5.2's capability by the end of 2026. That assumes continued benchmark gains and transfer to long, error-prone replication tasks; neither is guaranteed, and new architectures may need runtimes unavailable on old devices.

Earlier work already examined agents creating copies in prepared environments: a 2024 study used Llama 3.1 70B and Qwen 2.5 72B, while a later working paper evaluated 32 systems and reported successes down to 14 billion parameters. Its broader risk conclusions remain debated. Anthropic adds heterogeneous deployment evidence, not proof of spontaneous malicious intent. Small models' stronger coding than phishing performance also limits some propagation routes.

The practical threshold is a compact model repeatedly completing the whole loop on representative constrained hardware without an external orchestrator or pre-granted execution. Field evidence of weight-bearing malware would be another distinct signal. Ordinary malware calling an AI API is not the same architecture.

Existing device controls still matter

Mirai already demonstrated how weak default credentials can support conventional botnets. Removing exposed maintenance access, maintaining updates and segmenting reachable devices constrains both fixed and adaptive malware. The source cites UK manufacturer device-security guidance in discussing restrictions on universal default passwords.

Model transfers and abnormal local communication are useful monitoring targets; honeypots can capture payloads, while providers can isolate persistent scanning. Accelerator-equipped cameras, conferencing devices, storage appliances, development boards and robots deserve inventory, but visibility is not vulnerability: many use outbound management tunnels, and the report notes no historical mass compromise comparable to ordinary IoT botnets.

A blanket ban on local models would confuse an ingredient with an attack. Unauthorized access, persistence and propagation create the risk. Agent provisioning, credential copying, port opening and descendant launches instead warrant explicit privileges and auditable limits. The research establishes why those boundaries should be tested now, while preserving the decisive conclusion: adaptable installation and simplified propagation have been demonstrated separately; a self-contained worm across real IoT hardware has not.

Sources

Browse the directory →