LiteLLM Attack Affected 2,500 Companies, 434,000 CI/CD Pipelines: CloudSEK

Sicherheitsmeldung mit Schweregrad noch nicht bewertet. Technische Details im Tab „Originaltext“; empfohlene Schritte in der Checkliste.

Originaltext der Quelle (nicht übersetzt) – die deutsche Zusammenfassung findest du im Tab „Kurzfassung".

The massive supply-chain attack that compromised LiteLLM in the spring affected more than 2,500 companies and exposed about 434,000 CI/CD pipelines, with victims ranging from top-tier IT and AI companies to cybersecurity firms, SaaS, and enterprises. It rolled up a lot of victims, but also was a high-profile example of the growing trend of threat actors targeting companies’ AI infrastructure layer that is increasingly becoming connected to everything within their environments, according to CloudSEK threat researchers. The March attack on LiteLLM, a gateway and toolkit that lets developers call more than 100 large language model (LLM) providers – including Anthropic, Google’s Gemini, and Amazon Web Services’ (AWS’) Bedrock – was the result of the threat group TeamPCP earlier that month compromising Aqua Security’s Trivy open source security vulnerability scanner and its associated GitHub Actions. LiteLLM was compromised by TeamPCP but never directly attacked, according to CloudSEK’s researchers. Instead, LiteLLM became part of a much broader campaign by the threat group after its CI pipeline installed the compromised Trivy scanner, leading to the publishing of releases 1.82.7 and 1.82.8 that included malicious code to the Python Package Index (PyPI) repository. “Trivy, then the build system, then the LiteLLM release: one un-revoked token, three tools deep,” the CloudSEK researchers wrote in a report. “That chain is what turns a single credential leak into ecosystem-wide exposure.” Only 40 Minutes Were Needed The two malicious LiteLLM packages remained on PyPI for about 40 …

Vollständiger Originalartikel ↗

• Betroffenheit im eigenen Stack prüfen: Versionen/Komponenten abgleichen.
• Originalquelle / Hersteller-Advisory lesen: https://devops.com/litellm-attack-affected-2500-companies-434000-ci-cd-pipelines-cloudsek/
• Verfügbaren Patch oder Workaround einspielen und dokumentieren.