Analysis · curated 19 Sep 2026
npm Package Security in the Age of AI Agents: What Changed and What Catches It
First reported faun.dev
Coverage timeline
Single-source analysis — first reported, latest, and curated coincide.
Why it matters
Autonomous package installation by AI coding agents erases the manual review that underpinned npm security, letting slopsquatting and MCP-triggered RCE reach developer machines without any human or existing DevSecOps checkpoint.
An analysis piece argues that agentic AI coding assistants have removed the human checkpoint between dependency selection and installation, opening npm to two attack patterns: slopsquatting (attackers pre-registering the package names LLMs predictably hallucinate) and MCP RCE (a critical vulnerability in a widely used MCP bridge with 437K+ downloads that fires full remote code execution when a client autonomously connects to an untrusted server). It contends SAST and SCA cannot catch these and that detection must move to the registry and install/OS layer.