Skip to content

fix: pin liteLLM <=1.82.6 to mitigate TeamPCP supply chain attack#429

Open
gn00295120 wants to merge 1 commit intoNVIDIA:mainfrom
gn00295120:fix/pin-litellm-supply-chain
Open

fix: pin liteLLM <=1.82.6 to mitigate TeamPCP supply chain attack#429
gn00295120 wants to merge 1 commit intoNVIDIA:mainfrom
gn00295120:fix/pin-litellm-supply-chain

Conversation

@gn00295120
Copy link

Summary

liteLLM versions 1.82.7 and 1.82.8 were compromised by the TeamPCP group via a supply chain attack through Trivy. The current dependency constraint allows these malicious versions to be installed.

Impact

The compromised versions steal sensitive credentials including SSH keys, AWS/GCP/K8s credentials, CI/CD tokens, and environment variables. Version 1.82.8 installs a .pth persistence mechanism that executes on every Python startup — even after liteLLM is uninstalled.

Fix

This PR pins the upper bound of the liteLLM dependency to <=1.82.6, which is the last known safe version before the compromise. Once BerriAI publishes a verified clean release, this upper bound can be raised.

References

liteLLM versions 1.82.7 and 1.82.8 were compromised by the TeamPCP group
via a supply chain attack. This pins the upper bound to the last known
safe version.

References:
- BerriAI/litellm#24512
- https://osv.dev/vulnerability/MAL-2026-2144
Copilot AI review requested due to automatic review settings March 25, 2026 09:24
Copy link

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Pins the litellm dependency to avoid installing known-compromised versions (1.82.7/1.82.8) associated with the TeamPCP supply chain attack.

Changes:

  • Adds an upper-bound constraint to litellm in the Python project dependencies to prevent installation of compromised releases.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants