LiteLLM Supply Chain Attack: 2,500+ Companies Exposed in the Largest AI Supply Chain Breach of 2026

In March 2026, the threat actor group TeamPCP executed what is believed to be the largest supply chain attack targeting AI infrastructure by compromising LiteLLM through a chain that began with a compromised Trivy build. 

The attack cascaded through PyPI into automated CI/CD pipelines, exposing over 2,500 companies and 434,000 pipelines worldwide. The malicious package versions 1.82.7 and 1.82.8 were live for approximately 40 minutes, yet automated systems rapidly distributed the compromise. 

The stealer (SANDCLOCK) harvested SSH keys, cloud credentials (AWS, GCP, Azure), Kubernetes tokens, environment variables, CI/CD secrets, and LLM API keys. 

Notable exposed organizations include Amazon, Cisco, Samsung, Salesforce, Siemens, Airbus, FedEx, Deloitte, Twitter/X, Zscaler, and many others. 

The FBI's July 2026 FLASH advisory warns that affiliated actors are likely to weaponize the harvested credentials long after the original intrusion. The breach demonstrates how compromising an AI control point can expose entire enterprise identities and systems, signaling that future attacks will increasingly target AI infrastructure as a strategic junction between data, identity, and autonomous action. 

https://www.cloudsek.com/blog/ai-supply-chain-breach-2500-companies-434000-cicd-pipelines

Comments

Post a Comment

Popular posts from this blog

Prompt Engineering Demands Rigorous Evaluation

In the blog post “Prompt Engineering Requires Evaluation” on the Shostack + Associates website, the author argues that treating prompts for large language models (LLMs) merely as creative artefacts is insufficient. Engineering prompts properly demands structured evaluation frameworks — what the AI community calls “evals” — to test which prompt versions work better, with which models, and under which conditions. The post highlights that simply assuming a prompt is “good enough” creates risks when LLMs are integrated into production systems (e.g., for threat modeling). It advocates for measuring prompt performance, variation effects, and tool-chain dependencies (model, context, ancillary materials).  Ultimately the message is: prompt engineering should borrow disciplined practices from software engineering (versioning, testing, benchmarking) rather than relying on informal experimentation.  https://shostack.org/blog/prompt-enignieering-requires-evaluation/
Read more

Open-SPDD proposes an open framework for Spec-Driven Development workflows

Open-SPDD is an open-source project focused on Spec-Driven Product Development, aiming to formalize how software specifications, requirements, architecture, and implementation interact throughout the development lifecycle. The project promotes structured specification management, traceability, and AI-assisted engineering workflows, positioning itself as a foundation for “SpecOps”-style development practices. Its GitHub materials describe SPDD as a way to reduce ambiguity between planning and execution by treating specifications as first-class operational artifacts that can drive automation, validation, and collaboration across engineering teams  https://github.com/gszhangwei/open-spdd
Read more

OWASP ASVS 5.0 Released - Key Updates and What You Need to Know

The OWASP Foundation has released version 5.0 of the Application Security Verification Standard (ASVS), a major update to their security framework for web applications. This new version features restructured security requirements for better clarity, expanded guidance for cloud and API security, improved DevSecOps integration for CI/CD pipelines, updated threat modeling support, and enhanced compliance mapping with standards like NIST and PCI DSS. ASVS serves as a critical benchmark for developers building secure applications, penetration testers conducting security assessments, and auditors performing compliance reviews.  The standard is available for download from the OWASP ASVS project page, with organizations encouraged to integrate it into their software development lifecycles through code reviews and security testing tools. As a vendor-neutral, community-driven project, OWASP continues to welcome contributions to further develop the standard. This release represents an importa...
Read more