Your AI Coding Tools Are the Attack Surface: SANDWORM_MODE, Claude Code RCE, and the Trust Boundary Crisis
This is the most consequential security story of the week, confirmed across seven independent sources. Three distinct attack vectors are converging on your development pipeline simultaneously, and they all exploit the same architectural flaw: AI agents that can read untrusted content AND invoke privileged tools without hard isolation between the two.
The SANDWORM_MODE Worm
Socket's research team discovered a self-propagating npm worm spreading through 19 malicious packages that specifically targets AI coding assistants. The attack chain: exfiltrate crypto keys → raid password managers (Bitwarden, 1Password, LastPass) → inject malicious MCP servers into Claude, Cursor, VS Code Continue, and Windsurf. Every subsequent MCP tool call executes attacker-controlled code. The worm propagates via stolen npm/GitHub tokens and contains dormant capabilities including a polymorphic engine using local Ollama (deepseek-coder:6.7b) for self-rewriting and a destructive dead switch that wipes your home directory when access is revoked.
Claude Code CVEs
Anthropic's Claude Code has confirmed RCE vulnerabilities — CVE-2025-59536 and CVE-2026-21852 — where malicious Hooks and MCP server configurations in cloned repositories achieve code execution and API key theft. The critical shift: the threat model moved from 'running untrusted code' to 'opening untrusted projects.' Separately, Meta's Manus AI agent (SilentBridge, CVSS 9.8) demonstrated the same class: hidden instructions in web pages triggered Gmail exfiltration, reverse shells with passwordless sudo, and cross-tenant CDN access.
CI/CD Pipeline Compromise
Adnan Khan found that Cline's Claude-powered issue triage was vulnerable to prompt injection via GitHub issue titles, chaining to cache poisoning (using the Cacheract tool) → production release credential theft → VS Code Marketplace compromise affecting millions. A separate threat actor found Khan's PoC on his test repo and used it to attack Cline before responsible disclosure completed — threat actors are actively monitoring security researchers' public repos for weaponizable PoCs.
These aren't implementation bugs that better input validation would fix. They're architectural failures. Any agentic system without hard isolation between content processing and tool invocation is vulnerable to this entire class of attack.
The npm Preinstall Hook Vector
The ambar-src typosquatting attack hit 50,000 downloads in 3 days, deploying OS-specific payloads via preinstall hooks: encrypted shellcode on Windows, Golang reverse SSH on Linux, Apfell/MythicAgents on macOS, with Yandex Cloud C2. Combined with fake job-assessment repos deploying fileless multi-stage backdoors (confirmed by Microsoft), your entire code ingestion pipeline — from npm install to git clone to AI-suggested packages — is under active attack.
Defensive Tooling Worth Evaluating
| Tool | What It Does | Why It Matters |
|---|---|---|
| nono (Luke Hinds) | Kernel-level AI agent sandbox using Landlock/Seatbelt | Prompt injection cannot bypass kernel enforcement |
| enveil | Encrypts .env secrets with AES-256-GCM, injects only at subprocess launch | Prevents AI assistants from reading plaintext secrets in context |
| Titus (Praetorian) | Secret scanner with 450+ rules, binary file scanning | Catches secrets in Office docs, PDFs, SQLite that others miss |
What to do
Audit all MCP server configurations in Claude, Cursor, Windsurf, and VS Code Continue for unauthorized entries — check for SANDWORM_MODE indicators: unexpected npm deps, modified git hooks, unrecognized MCP servers
Enable --ignore-scripts for npm install in all CI pipelines and audit every preinstall hook exception by end of week
Establish sandboxed environment policy for all external code evaluation — candidate repos, OSS projects, AI-suggested packages — using ephemeral VMs with no network egress to internal infrastructure
Evaluate nono kernel-level sandbox for all AI coding tools with file system or network access this quarter
Implement package signature verification and allowlist policies for npm, NuGet, and PyPI in CI/CD — audit for malicious 'StripeApi' NuGet package across all .NET projects immediately