LiteLLM Master Key Leak Leads to Malicious Package Release
LiteLLM
An accidentally published master key allowed attackers to compromise a release pipeline and push a malicious Python package. The incident highlights supply chain risks associated with exposed AI platform credentials.
- fix status
- Fix status unknown
- first report
- 24 Oct 2026
- last update
- 26 Oct 2026
Timeline · 2
Sources · 2
News and write-ups
- 2026-10-24Leaked LiteLLM Master Key Let Attackers Steal GitHub Tokens and Hijack Release PipelineThe Hacker News · thehackernews.com/2026/10/leaked-litellm-master-key-let-attackers.html
- 2026-10-26Popular AI tool LiteLLM says unrevoked key allowed hackers to target usersThe Record · therecord.media/litellm-hackers-ai-malware
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 chainAgent hijackData leak
- severity
- 3 · Confirmed exploitation
- fix status
- Fix status unknown
- targets
- Framework / tooling
- owasp llm top 10
- LLM02:2025 Sensitive Information DisclosureLLM03:2025 Supply ChainLLM06:2025 Excessive Agency
- dates
- happened 24 Oct 2026 · first reported 24 Oct 2026
- origin
- News & research feeds
- record
- confidence 0.95 · created 2026-10-24 16:11Z · updated 2026-11-10 00:11Z
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 Master Key Leak Leads to Malicious Package Release https://gcdradar.vercel.app/incidents/litellm-master-key-leak-leads-to-malicious-package-release · AIR-2026-1496 · closed 2026-11-09 - Lane: Supply chain - Severity: 3 (Confirmed exploitation) - Fix status: Fix status unknown - First reported: 2026-10-24 - AI role: Attack on AI - Products: LiteLLM ## Summary An accidentally published master key allowed attackers to compromise a release pipeline and push a malicious Python package. The incident highlights supply chain risks associated with exposed AI platform credentials. ## What to do No action recorded; read the sources below and the vendor's advisory. ## Latest updates - 2026-10-26: Vendor confirms an unrevoked key accidentally exposed in May caused the supply-chain attack (https://therecord.media/litellm-hackers-ai-malware) - 2026-10-24: Leaked LiteLLM Master Key Let Attackers Steal GitHub Tokens and Hijack Release Pipeline (https://thehackernews.com/2026/10/leaked-litellm-master-key-let-attackers.html) ## Sources - 2026-10-24 The Hacker News: Leaked LiteLLM Master Key Let Attackers Steal GitHub Tokens and Hijack Release Pipeline https://thehackernews.com/2026/10/leaked-litellm-master-key-let-attackers.html - 2026-10-26 The Record: Popular AI tool LiteLLM says unrevoked key allowed hackers to target users https://therecord.media/litellm-hackers-ai-malware Verify against the vendor's advisory before changing production. Data CC BY-SA 4.0, https://gcdradar.vercel.app.
Related
- closedopen-weight LLM Model-as-a-Trojan: Self-Activating Covert DNS Exfiltration in LLM Weights
Research · since 19 Oct 2026
AI - closedMCP servers & tools Postmark MCP Server Package Hijacked for Email Exfiltration
Supply chain · Exploited · since Sep 2025 (approx.)
AI - liveOpenAI Codex OpenAI Codex Jailbreak Toolkit Hides Prompt Adware to Hijack AI Agents
Research · since 4 Nov 2026
AI - liveLLM Agent Frameworks Beyond Prompt Injection: The Tool Update Gap in LLM Agent Security
Research · since 3 Nov 2026
AI - liveMCP SDKs MCP Tool Poisoning in Agentic AI Frameworks Across Multiple Frameworks
Research · since 3 Nov 2026 · updated 5 Nov 2026
AI - closedSteering Vectors Steering for Safety, Hijacking for Profit: Trojan Threats in LLM Steering
Research · since 27 Oct 2026
AI