BREACH WATCH BRIEF High ☁️ Breach

Supply Chain Attack Compromises LiteLLM PyPI Package, Distributing Credential‑Stealing Malware to Millions of Developers

Hackers breached the LiteLLM open‑source project's release pipeline and published a malicious 1.107.0 wheel on PyPI and compromised Docker images. The payload steals cloud, AI, and developer credentials, exposing any organization that installs the package. This highlights the need for continuous third‑party risk monitoring and software‑integrity controls for audit readiness.

SeverityHigh
Type☁️ Breach
ConfidenceHigh
ReportedOct 22, 2026
Technology & SaaS Technology and SaaS vendors Cloud‑native development teams AI/ML engineering groups Third-Party Dependency Supply Chain Attack
Check if you use it. This incident came through a third party or the supply chain. If the product or supplier is in your estate or your vendors', start with the questions to ask below.

What happened

On October 21 2026 the LiteLLM maintainers discovered that their CI/CD pipeline had been compromised. Attackers pushed a malicious version 1.107.0 to PyPI and to Docker Hub/GHCR. The wheel contained three hidden files that execute on Python start‑up, harvesting cloud and AI credentials. The compromised Docker images were removed within hours after detection.

Why it matters for trust and compliance

  • The breach underscores the importance of a control‑assurance program that continuously validates third‑party software integrity, records evidence of package signing, and maintains an audit‑ready trail of supply‑chain risk assessments.
  • Provides concrete evidence for the ‘software‑supply‑chain integrity’ control objective across frameworks.
  • Enables organizations to demonstrate due‑diligence and continuous monitoring of third‑party releases during audits.

Who is affected

Technology and SaaS vendors Cloud‑native development teams AI/ML engineering groups

Recommended actions

  1. Block and remove LiteLLM version 1.107.0 from all internal repositories.
  2. Scan environments for the malicious `cook.pth`, `cook.py`, and `sitecustomize.py` files.
  3. Implement signed package verification and SBOM checks for all third‑party dependencies.
  4. Integrate automated monitoring of upstream releases into your vendor risk management workflow.

Regulations library

Every US state privacy law, on one map

24 states have a comprehensive privacy law in the library, alongside the EU, UK, US federal and global laws: 102 in all, each explained in plain words with its sources. Select a state to see what applies there.

  • In force
  • Coming into force
  • Sector laws
AK ME VT NH WA ID MT ND MN IL WI MI NY RI MA OR NV WY SD IA IN OH PA NJ CT CA UT CO NE MO KY WV VA MD DE AZ NM KS AR TN NC SC DC OK LA MS AL GA HI TX FL

Get the Breach Digest

The incidents that matter for your vendors and your data, analysed for practitioners, in one email.