[REVISION HISTORY]
LiteLLM supply chain attack
2 recorded revisions of this situation.
What changed
2026-08-18 21:47 UTC → 2026-08-21 18:26 UTC ·
added
removed
A software supply chain attack targeted LiteLLM, an open-source AI gateway, potentially exposing credentials for over 2,500 organizations. The breach occurred when attackers compromised the release process for the Trivy scanner, allowing poisoned code to enter the LiteLLM build pipeline and produce malicious packages on the Python Package Index (PyPI). Malicious versions 1.82.7 and 1.82.8 were available for a limited window. While initial estimates suggested a five-day impact, researchers from SOCRadar identified that these specific versions were hosted on PyPI for approximately 40 minutes in on March 24, 2026. The intrusion exploited a lack of identity verification during LiteLLM’s automated processes, granting attackers server administrator privileges to install data-collecting software. Version 1.82.8 utilized a .pth startup file, enabling malicious code to execute automatically whenever the Python interpreter launched, even without a direct library import. launched. This expanded the risk to organizations using LiteLLM indirectly through frameworks such as CrewAI, DSPy, and MLflow. The malware was designed to steal sensitive data, including cloud keys, SSH keys, Kubernetes tokens, database passwords, and LLM API keys for services like OpenAI and Anthropic. During the compromise, the malware reportedly harvested approximately 434,000 CI/CD files, including credentials for AWS, Google Cloud, and Azure. Stolen data was exfiltrated to a typosquat domain, models.litellm.cloud. Analysts from CloudSEK and Hudson Rock have attributed the campaign to the group TeamPCP (also tracked as UNC6780). While major entities such as NVIDIA, Cisco, Samsung, Amazon Web Services, Volkswagen, and Volkswagen the London Stock Exchange Group were identified as potentially affected, researchers noted note that exposure does not confirm a successful breach for every named organization. Experts and security firms advise affected parties to rotate all credentials immediately. immediately, though researchers warn that some compromised keys may remain valid.
Versions
- 2026-08-21 18:26 UTC LiteLLM supply chain attack
- 2026-08-18 21:47 UTC LiteLLM supply chain attack
- 2026-08-17 05:20 UTC LiteLLM supply chain attack
Select a version to see what changed compared to the one before it.