LiteLLM Compromised in Supply Chain Attack Delivering Credential Stealer and Backdoor
Overview
The LiteLLM Python package has been compromised in a supply chain attack, resulting in the distribution of a credential stealer and a backdoor. This compromise specifically affects version 1.107.0 of LiteLLM, which was available through PyPI wheels and Docker images. Security researchers from SafeDep, Socket, StepSecurity, and Upwind have reported the incident, leading to the quarantining of the affected package on the Python Package Index (PyPI). This situation raises concerns for developers and organizations using the package, as it could potentially expose sensitive information and backend access to attackers. Users are advised to avoid the compromised version and check for any unauthorized access in their systems.
Key Takeaways
- Active Exploitation: This vulnerability is being actively exploited by attackers. Immediate action is recommended.
- Affected Systems: LiteLLM 1.107.0, distributed through PyPI and Docker images
- Action Required: Users should avoid using LiteLLM version 1.
- Timeline: Newly disclosed
Original Article Summary
The popular LiteLLM Python package has been compromised as part of a software supply chain attack that delivered a credential stealer and a backdoor, according to reports from SafeDep, Socket, StepSecurity, and Upwind. The compromise affects LiteLLM 1.107.0, distributed through PyPI wheels and Docker images. The Python package has since been quarantined on Python Package Index (PyPI), and the
Impact
LiteLLM 1.107.0, distributed through PyPI and Docker images
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 should avoid using LiteLLM version 1.107.0 and monitor their systems for unauthorized access.
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.