The malicious PyPI package and Docker images were published through the project's own release process, meaning anyone who pulled the affected versions during the exposure window may have run the payload. The stolen data set includes credentials, secrets, and environment variables — exactly the material that grants further access to cloud accounts, CI/CD systems, and downstream services.

If you use LiteLLM, treat any install or container pull from the affected period as potentially compromised:

• Audit dependency versions and image digests pulled recently against the project's official advisories
• Rotate credentials, API keys, secrets, and environment variables exposed to affected environments
• Review CI/CD and cloud logs for anomalous activity from hosts running the package or images
• Pin to verified versions and digests once the maintainers confirm clean releases

The project has not yet published a full timeline of the compromised release window, so teams should monitor its official channels for updates before reinstalling.

Source: Unknown

Has your organization pulled any LiteLLM packages or images recently, and have you rotated the secrets they could reach?