LiteLLM PyPI Supply Chain Compromise — v1.82.7/v1.82.8 Steal Credentials via Malicious Code

What this error means

litellm PyPI package (v1.82.7 + v1.82.8) compromised — credential theft via malicious code in proxy_server.py and litellm_init.pth is a LiteLLM failure pattern reported for developers trying to check if litellm package is safe / recover from compromised pypi install. Based on the imported evidence, treat this as a tool-specific troubleshooting page rather than a generic API error.

Why this happens

116 comments on GitHub issue. Compromised versions published by attacker who hijacked maintainer PyPI account. Malicious code exfiltrates credentials to attacker-controlled litellm.cloud domain. PyPI package suspended, current releases clean. Engaged Mandiant for investigation.

Common causes

• LiteLLM is a widely-used AI gateway/proxy. The PyPI package was hijacked, publishing malicious versions that steal SSH keys, API keys, AWS/GCP/Azure credentials, and crypto wallets. Developers using pip install litellm during the compromise window were infected.
• 116 comments on GitHub issue. Compromised versions published by attacker who hijacked maintainer PyPI account. Malicious code exfiltrates credentials to attacker-controlled litellm.cloud domain. PyPI package suspended, current releases clean. Engaged Mandiant for investigation.

Quick fixes

1. Confirm the exact error signature matches litellm PyPI package (v1.82.7 + v1.82.8) compromised — credential theft via malicious code in proxy_server.py and litellm_init.pth.
2. Check the LiteLLM account, local tool state, and provider configuration involved in the failing workflow.
3. Compare the failing environment with a known working setup, then change one configuration value at a time.

Platform/tool-specific checks

• Verify the command, editor, extension, or API client that produced the error.
• Compare local settings with CI, deployment, or editor-level settings when the error appears in only one environment.
• Avoid deleting credentials, local model data, or project settings until the failing scope is clear.

Step-by-step troubleshooting

1. Capture the exact error message and the command, editor action, or request that triggered it.
2. Check whether the failure is account/auth, quota/rate, model/provider, local runtime, or deployment configuration.
3. Review the source evidence below and compare it with your environment.
4. Apply one change at a time and rerun the smallest failing action.
5. Keep the working fix documented for the team or deployment environment.

How to prevent it

• Keep provider/tool configuration documented.
• Record non-secret diagnostics such as tool version, provider name, model name, and command path.
• Add a lightweight check before CI or production workflows depend on the tool.

Sources checked

• https://github.com/BerriAI/litellm/issues/24518
• https://github.com/BerriAI/litellm/issues/24512
• https://news.ycombinator.com/item?id=47501729

Evidence note: 116 comments on GitHub issue. Compromised versions published by attacker who hijacked maintainer PyPI account. Malicious code exfiltrates credentials to attacker-controlled litellm.cloud domain. PyPI package suspended, current releases clean. Engaged Mandiant for investigation.

Related errors

• litellm proxy Docker image supply chain verification
• PyPI account hijacking detection for Python packages
• CI/CD pipeline compromise indicators

FAQ

What should I check first?

Start with the exact litellm PyPI package (v1.82.7 + v1.82.8) compromised — credential theft via malicious code in proxy_server.py and litellm_init.pth text and the smallest action that reproduces it.

Can I ignore this error?

No. Treat it as a failed LiteLLM workflow until the root cause is understood.

Is this guaranteed to have one fix?

No. The imported evidence supports the troubleshooting path above, but tool behavior can vary by account, plan, version, provider, and local configuration.

How do I know the fix worked?

Rerun the same command, editor action, or request. The fix is working when that action completes without litellm PyPI package (v1.82.7 + v1.82.8) compromised — credential theft via malicious code in proxy_server.py and litellm_init.pth.