The attack on the widely used LightLLM package demonstrates a major software supply chain vulnerability. Malicious code inserted into a routine update silently stole credentials from countless AI tools, a risk that will be amplified by autonomous AI agents.

A novel vulnerability arises when an AI agent references a package name that doesn't exist. Malicious actors can register these hallucinated package names and upload malicious code. This creates a documented supply chain attack vector that requires specific checks beyond typical static analysis to mitigate.

A cyberattack on AI training data provider Mercore highlights a major supply chain risk. Since Mercore provides expert contractors to labs like OpenAI and Anthropic, the breach could expose not just data, but the proprietary methodologies behind how frontier models are trained.

Inspired by ESG's Scope 3, which assesses supplier impact, building secure AI requires preemptively vetting the entire software supply chain. Companies must treat open-source packages and dependencies as suppliers, ensuring every component is secure from the start, rather than reactively scanning for flaws.

The massive increase in AI-generated code is simultaneously creating more software dependencies and vulnerabilities. This dynamic, described as 'more code, more problems,' significantly expands the attack surface for bad actors and creates new challenges for software supply chain security.

MLOps pipelines manage model deployment, but scaling AI requires a broader "AI Operating System." This system serves as a central governance and integration layer, ensuring every AI solution across the business inherits auditable data lineage, compliance, and standardized policies.

The plummeting cost of finding exploits via AI models means enterprises cannot simply patch vulnerabilities reactively. The necessary strategic shift is to build foundational security controls for each asset class, including a new, dedicated security layer specifically for the AI stack.

Unlike traditional software, AI agents can compose new dependencies on the fly by loading external tools, installing packages, or altering infrastructure. This creates a dynamic, multilayered supply chain risk that evolves at runtime and cannot be managed with static vulnerability scans alone.

To manage risks from 'shadow IT' or third-party AI tools, product managers must influence the procurement process. Embed accountability by contractually requiring vendors to answer specific questions about training data, success metrics, update cadence, and decommissioning plans.