Skip to content
All posts
Topic

Litellm

4 articles on litellm.

LiteLLM 1.107.0 Was Backdoored: The Python .pth Trick That Stole Keys Before the Library Even Loaded (Oct 2026)
On 21 October 2026, malicious LiteLLM 1.107.0 artifacts hit PyPI, Docker Hub and GHCR. The payload ran at Python startup via a .pth file — no import needed — and exfiltrated cloud, AI, SSH and GPG credentials to a look-alike domain. What happened, the IOCs, and exactly what a security team should do now.
October 21, 2026
CISA Flags LiteLLM CVE-2026-59822: Attackers Forge Authenticated MCP Sessions With No Credentials
CISA added LiteLLM CVE-2026-59822 (CVSS 8.8) to its Known Exploited Vulnerabilities catalog on Sep 3, 2026 — an unauthenticated attacker can establish an authenticated MCP session against the popular AI gateway. Why the gateway is the prize, and how to respond.
September 3, 2026
Attackers Are Hunting Your AI Gateway: Inside the LiteLLM / RAGFlow / Kestra Campaign
Microsoft detailed a coordinated campaign (Aug 2026) hitting exposed AI infrastructure — LiteLLM, RAGFlow, Kestra — to steal every model-provider API key and then mine crypto on the box. The CVEs, the credential-harvesting playbook, and how to lock your AI control points down.
August 26, 2026
The LiteLLM Supply Chain Attack: What TeamPCP Stole, Who It Hit, and What to Do Now
Backdoored LiteLLM 1.82.7 and 1.82.8 stayed on PyPI for 40 minutes in March 2026 — long enough to compromise over 2,400 organizations. A 153GB archive of the stolen data has now surfaced. Here is exactly what happened, the IOCs, and the remediation checklist.
August 13, 2026
🎉 New here? Use code WELCOME10 for 10% off any plan at checkout
Litellm — Articles & Guides | PlayCISO Blog · PlayCISO