Seven Attacks, One Pattern: Why the Development Environment Is Now in the Crosshairs

About this Whitepaper

Between October 2025 and April 2026, seven separate attacks hit six different layers of the software development environment: the local machine and IDE, source code management, CI/CD pipelines, the dependency and package ecosystem, the AI toolchain, and deployment and cloud integration. Different groups, different techniques, one consistent target: the part of the stack where code is written, built, tested, and shipped — and where the most sensitive context about how systems work now lives.

This whitepaper maps GlassWorm, ForceMemo, the Trivy/TeamPCP campaign, Axios, LiteLLM, Lovable, and the Vercel/Context.ai incident to the layers they targeted, and explains what the pattern means for the enterprise threat model.

• 433 components compromised in the GlassWorm campaign — 72 VS Code extensions, 88 npm packages, and 151+ repositories, with over 9 million malicious installs
• 3 hours — how long backdoored versions of Axios, a package with 100M+ weekly downloads, were live before removal
• 48 days — the window in which Lovable projects’ source code, credentials, and full AI chat histories remained exposed after first report

The whitepaper also covers why the standard incident response playbook does not fully apply to development environment compromise, why remediation is a graph traversal problem rather than a checklist, and the two controls that limit blast radius: credential scoping and patch velocity calibrated to blast radius.