Home / Companies / Socket / Blog / Post Details
Content Deep Dive

LiteLLM PyPI Package and Docker Images Compromised to Steal Cloud and AI Credentials

Blog post from Socket

Post Details
Company
Date Published
Author
Socket Research Team
Word Count
2,314
Company Posts That Month
24
Language
English
Hacker News Points
-
Post removed?
No
Summary

Security researchers reported that LiteLLM version 1.107.0, distributed through PyPI and several Docker image tags on October 21, 2026, contained malicious Python startup files designed to collect cloud credentials, API keys, private keys, browser data, AI-tool authentication files, environment variables, and LiteLLM proxy database credentials. The malware could execute during normal Python startup through .pth and sitecustomize hooks even if LiteLLM was not imported, and it encrypted collected data before sending it to a purported LiteLLM health-check endpoint. A separate loader could periodically retrieve and execute unsigned remote Python code based on a GitHub-hosted domain pointer. Container provenance linked the affected build to a lookalike repository, Berri-AI/litellm, rather than the legitimate BerriAI/litellm repository, although the investigation could not determine how the source override was authorized or conclusively establish the PyPI publishing path. Users are advised to stop deploying the affected version and floating image tags, isolate systems where Python ran after installation, preserve evidence, rotate potentially exposed secrets from clean environments, and rebuild using reviewed artifacts and pinned container digests.

Trends Found in this Post
Trend Post Mentions Total Month Mentions Posts Companies MoM
Secrets Management 5 3,067 602 152 +50%
LLM 2 6,536 1,233 232 +8%
AI Coding Assistant 1 1,951 537 146 +22%
Kubernetes 1 5,108 488 113 +17%
MCP 1 11,815 1,211 231 +12%
Serverless 1 1,365 320 107 +12%
Use This Data

Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.