LiteLLM Package Compromised in Supply Chain Incident via Release Pipeline
LiteLLM
Threat actors compromised LiteLLM release pipelines to push a malicious package version containing a credential stealer to PyPI and Docker Hub. The incident resulted from compromised security controls and suspected token leaks in AI gateway logs.
- fix status
- Fix status unknown
- first report
- 22 Oct 2026
- last update
- 22 Oct 2026
Timeline · 1
Sources · 1
News and write-ups
- 2026-10-22LiteLLM Suspects GitHub Token Leak in AI Gateway Logs Behind Malicious Package ReleaseThe Hacker News · thehackernews.com/2026/10/litellm-suspects-github-token-leak-in.html
Titles and links belong to their publishers. The summary above is written by gcdRadar in its own words; data is CC BY-SA 4.0.
Classification
- lane
- Supply chain
- AI role
- Attack on AI
- categories
- Supply chain
- severity
- 3 · Confirmed exploitation
- fix status
- Fix status unknown
- targets
- Framework / tooling
- owasp llm top 10
- LLM03:2025 Supply Chain
- mitre atlas
- AML.T0010 AI Supply Chain Compromise
- dates
- happened 21 Oct 2026 · first reported 22 Oct 2026
- origin
- News & research feeds
- record
- confidence 0.95 · created 2026-10-22 12:03Z · updated 2026-11-06 00:23Z
Lane, AI role, categories and severity come from the classifier; the OWASP and ATLAS rows are derived from the categories. How these are assigned
Copy a brief
This record as a short Markdown brief, for a ticket, a chat or a coding agent.
the brief as text
# LiteLLM Package Compromised in Supply Chain Incident via Release Pipeline https://gcdradar.vercel.app/incidents/litellm-package-compromised-in-supply-chain-incident-via-rel · AIR-2026-1466 · closed 2026-11-05 - Lane: Supply chain - Severity: 3 (Confirmed exploitation) - Fix status: Fix status unknown - First reported: 2026-10-22 (happened 2026-10-21) - AI role: Attack on AI - Products: LiteLLM ## Summary Threat actors compromised LiteLLM release pipelines to push a malicious package version containing a credential stealer to PyPI and Docker Hub. The incident resulted from compromised security controls and suspected token leaks in AI gateway logs. ## What to do No action recorded; read the sources below and the vendor's advisory. ## Latest updates - 2026-10-22: LiteLLM Suspects GitHub Token Leak in AI Gateway Logs Behind Malicious Package Release (https://thehackernews.com/2026/10/litellm-suspects-github-token-leak-in.html) ## Sources - 2026-10-22 The Hacker News: LiteLLM Suspects GitHub Token Leak in AI Gateway Logs Behind Malicious Package Release https://thehackernews.com/2026/10/litellm-suspects-github-token-leak-in.html Verify against the vendor's advisory before changing production. Data CC BY-SA 4.0, https://gcdradar.vercel.app.
Related
- closedLiteLLM LiteLLM Master Key Leak Leads to Malicious Package Release
Supply chain · Exploited · since 24 Oct 2026 · updated 26 Oct 2026
AI - closedLiteLLM LiteLLM 1.107.0 compromised via malicious Python startup hooks
Supply chain · Exploited · since 23 Oct 2026
AI - closedLiteLLM LiteLLM release pipeline compromised to distribute info-stealer malware
Supply chain · Exploited · since 22 Oct 2026
AI - closedLiteLLM LiteLLM Compromised in Supply Chain Attack Delivering Credential Stealer
Supply chain · Exploited · since 21 Oct 2026 · updated 27 Oct 2026
AI - liveTrained to betray: How post-training supply chain attacks hijack coding agents
Research · since 12 Nov 2026
AI - liveLLM Agent StealthyPoison: Manipulating LLM Agent Behavior through Procedural Poisoning of Third-Party Skills
Research · since 10 Nov 2026
AI