Skip to content
AgentProv

2026-08-25 · 2026-Q3

ToxNetV2 Wires an NVIDIA-Hosted LLM Into a Linux Botnet's Command Loop

Outside the model: Offensive useAgent tooling was not the attack surface, so no layer applies.

Fixable
Unknown
Vendor response
Unknown
In the wild
Yes
Actor
Not applicable

Target

AArch64 Linux hosts, through a peer-to-peer botnet built on the Tox protocol

Impact

JoeSecurity analysts documented ToxNetV2, a Linux botnet whose controller sends live host and botnet telemetry, processes, CPU load, memory, and disk usage, to an NVIDIA NIM-hosted `z-ai/glm-5.2` model and parses the reply into structured `ACTION:` records queued as pending tasks. The parsed action set spans low-risk operations such as logging, alerts, memory storage, and task-weight changes alongside `shell_cmd`, `write_file`, `ssh_check`, and `compile_deploy`, meaning local shell execution, file writes, remote SSH commands, persistent state changes, and cross-compilation. The malware uses an "ENI/VEIL" prompt-injection preamble to reduce model refusals. The AI component sits inside a fuller architecture of encrypted peer-to-peer command and control, propagation logic, scanning workers, host-control features, and 17 network-attack launchers. ToxNetV2 is not a self-driving worm: higher-impact suggestions execute only after an authenticated operator issues the `aiexec` command. The notable part is placement, the model's output is attached to a live controller workflow rather than limited to code generation before deployment

Root cause

A hosted inference API reachable by any client with a key, wired directly into an attack controller's decision loop, with a jailbreak preamble standing in for guardrail removal. The operator-approval gate is the only thing separating this design from an autonomous one

Sources

Catalog

Cite this: AgentProv incident record: ToxNetV2 Wires an NVIDIA-Hosted LLM Into a Linux Botnet's Command Loop (2026-08-25). https://agentprov.com/incidents/2026-08-25-toxnetv2-wires-an-nvidia-hosted-llm-into-a-linux-botnet-s-command-loop