Malicious LiteLLM PyPI Releases Stole Cloud/K8s Creds from 2,100+ Orgs

Wed, 12 Aug 2026 11:57:00 +0000

Engineer — Act: If LiteLLM was installed in any environment during March 2026, assume cloud keys, SSH keys, and Kubernetes tokens from that system were exfiltrated — rotate all credentials from affected hosts and audit CI/CD pipeline logs for installs during that window.
SOC/IR — Act: Hunt for anomalous cloud API activity and Kubernetes token usage dating back to March 2026 on any host where LiteLLM was installed; CloudSEK’s 434,000-file dataset suggests usable IOC context is emerging, so watch for actor TTPs tied to the Trivy campaign.
Leader — Act: Confirm with engineering whether LiteLLM or Trivy are in use in the AI/ML stack; if so, direct a credential-rotation audit this week and assess whether any customer data environments were reachable from affected systems — 2,100+ exposed organizations makes this a peer-company disclosure risk worth tracking.

Pypi on CuraSec