Skip to content
ThreatCluster

AI Agent Vulnerability: Remote Code Execution via Pretraining Data Poisoning

First seen 31 Oct 2026, 16:43 UTC • •

Article Content

Browse articles
ThreatCluster AI
ThreatCluster •October 31, 2026 at 18:13 UTC
  • •0.1% data poisoning can lead to a 92% success rate for remote code execution attacks.
  • •The attack survives clean post-training processes, challenging traditional defense methods.
  • •Ordinary file paths can serve as triggers, complicating detection and mitigation efforts.

A recent paper from Anthropic reveals that poisoning just 0.1% of pretraining data can create a remote code execution backdoor in AI agents, specifically in Qwen3 models. The attack succeeds on approximately 92% of triggered prompts, even after the models undergo clean post-training processes. The backdoor can be triggered by ordinary file paths in user requests, making it difficult to filter out malicious inputs. The study highlights two novel methods for data poisoning: declaration-based poison and ordinary-string triggers. These findings suggest that relying solely on clean post-training does not eliminate pretraining poison. The practical defense measures include sandboxing, least privilege access, and requiring human approval for risky commands. This research raises significant concerns about the security of AI agents in operational environments.

Start a free Starter trial for enhanced analysis

Ask AI about this cluster

Updated just now How this analysis works

Timeline

2026-10-30
Anthropic paper published
Anthropic's research paper details how poisoning pretraining data can create backdoors in AI agents, demonstrating significant vulnerabilities.
X
2026-10-30
Discussion on findings
Cybersecurity experts discuss the implications of the Anthropic paper, emphasizing the alarming ease of executing remote code via poisoned data.
X

More articles in this cluster (2)

Common questions

What models are affected?
The Qwen3 models, including 0.6B, 1.7B, and 4B architectures, are specifically mentioned as vulnerable.
How can organizations defend against this?
Implementing sandboxing, least privilege access, and requiring human approval for commands can help mitigate risks.
Is this vulnerability actively exploited?
No confirmed exploitation has been reported; the findings are based on research rather than active incidents.