TeamPCP Backdoors LiteLLM Versions 1.82.7–1.82.8 Likely via Trivy CI/CD Compromise
Overview
TeamPCP, a known threat actor, has compromised the popular Python package litellm by injecting malicious code into versions 1.82.7 and 1.82.8. This compromise was linked to earlier incidents involving the Trivy and KICS tools. The malicious versions contain a credential harvester, a toolkit for lateral movement within Kubernetes environments, and a persistent backdoor. Security companies like Endor Labs and JFrog have confirmed the issue, raising concerns for developers and organizations using this package. The presence of these backdoors could allow attackers to gain unauthorized access to sensitive information and systems, making it crucial for users to act quickly to protect their environments.
Key Takeaways
- Active Exploitation: This vulnerability is being actively exploited by attackers. Immediate action is recommended.
- Affected Systems: litellm versions 1.82.7 and 1.82.8
- Action Required: Users are advised to remove versions 1.
- Timeline: Newly disclosed
Original Article Summary
TeamPCP, the threat actor behind the recent compromises of Trivy and KICS, has now compromised a popular Python package named litellm, pushing two malicious versions containing a credential harvester, a Kubernetes lateral movement toolkit, and a persistent backdoor. Multiple security vendors, including Endor Labs and JFrog, revealed that litellm versions 1.82.7 and 1.82.8 were published on
Impact
litellm versions 1.82.7 and 1.82.8
Exploitation Status
This vulnerability is confirmed to be actively exploited by attackers in real-world attacks. Organizations should prioritize patching or implementing workarounds immediately.
Timeline
Newly disclosed
Remediation
Users are advised to remove versions 1.82.7 and 1.82.8 of litellm immediately and upgrade to a safe version.
Additional Information
This threat intelligence is aggregated from trusted cybersecurity sources. For the most up-to-date information, technical details, and official vendor guidance, please refer to the original article linked below.
Related Topics: This incident relates to Malware.