WeaknessASC-2026-0059Other weakness
Unpinned AI dependencies and compromised maintainer releases
MediumFixed
Floating version ranges pull a malicious release as soon as a maintainer account or release pipeline is compromised, as the Ultralytics releases on PyPI (December 2024) and the Shai-Hulud worm on npm (September 2025) showed.
How to detect it
- Version ranges instead of pinned versions
- Installs that run lifecycle scripts
How to resolve it
- Pin exact versions with lockfiles and hashes
- Delay adoption of new releases by a few days
- Disable install scripts by default
How to investigate
- Check whether a compromised version was installed anywhere
- Rotate credentials on affected machines and CI
Sources
- Python Software Foundation: Supply-chain attack analysis: Ultralytics (December 2024)
- CISA: Widespread Supply Chain Compromise Impacting npm Ecosystem (September 2025)
- OWASP Top 10 for LLM Applications 2025: LLM03 Supply Chain
- OWASP Top 10 for Agentic Applications 2026: ASI04 Agentic Supply Chain Vulnerabilities
- MITRE ATLAS: AML.T0010 AI Supply Chain Compromise