Wow this is in a lot of software
Tell HN: Litellm 1.82.7 and 1.82.8 on PyPI are compromised
31–40 of 569 posts
Re: Tell HN: Litellm 1.82.7 and 1.82.8 on PyPI are compromised
#32Re: Tell HN: Litellm 1.82.7 and 1.82.8 on PyPI are compromised
#33Our modern economy/software industry truly runs on egg-shells nowadays that engineers accounts are getting hacked to create a supply-chain attack all at the same time that threat actors are getting more advanced partially due to helps of LLM's.
First Trivy (which got compromised twice), now LiteLLM.
Re: Tell HN: Litellm 1.82.7 and 1.82.8 on PyPI are compromised
#34Thank you for posting this, interesting. I hope that everyone's course of action will be uninstalling this package permanently, and avoiding the installation of packages similar to this. In order to reduce supply chain risk not only does a vendor (even if gratis and OS) need to be evaluated, but the advantage it provides. Exposing yourself to supply chain risk for an HTTP server dependency is natural. But exposing yo…
> Remember that you are programmers and you can just program, you don't need a framework, you are already using the API of an LLM provider, don't put a hat on a hat, don't get killed for nothing.
Programming for different LLM APIs is a hassle, this library made it easy by making one single API you call, and in the backstage it handled all the different API calls you need for different LLM providers.
Re: Tell HN: Litellm 1.82.7 and 1.82.8 on PyPI are compromised
#35title is bit misleading.
The package was directly compromised, not “by supply chain attack”.
If you use the compromised package, your supply chain is compromised.
Re: Tell HN: Litellm 1.82.7 and 1.82.8 on PyPI are compromised
#36I just installed Harbor, and it instantly pegged my cpu.. i was lucky to see my processes before the system hard locked.
Basically it forkbombed `grep -r rpcuser\rpcpassword` processes trying to find cryptowallets or something. I saw that they spawned from harness, and killed it.
Got lucky, no backdoor installed here from what i could make out of the binary
Re: Tell HN: Litellm 1.82.7 and 1.82.8 on PyPI are compromised
#37Now I feel lucky that I switched to just using OpenRouter a year ago because LiteLLM was incredible flaky and kept causing outages.
Re: Tell HN: Litellm 1.82.7 and 1.82.8 on PyPI are compromised
#38Look like the Founder and CTO account has been compromised. https://github.com/krrishdholakia
Most his recent commits are small edits claiming responsibility on behalf of "teampcp", which was the group behind the recent Trivy compromise: https://news.ycombinator.com/item?id=47475888
I was just wondering why the Trivy compromise hit only npm packages, thinking that bigger stuff should appear sooner or later. Here we go...
Re: Tell HN: Litellm 1.82.7 and 1.82.8 on PyPI are compromised
#39Someone needs to go to prison for this.
Re: Tell HN: Litellm 1.82.7 and 1.82.8 on PyPI are compromised
#40Earlier quoted context omitted.
In case you missed it, according to the OP, the previous point release (1.82.7) is also compromised.
Yeah, that release has the base64 blob, but it didn't contain the pth file that auto triggers the malware on import.
The latest version with the the pth file doesn't require an import to trigger the exploit (just having the package installed is enough thanks to [1]).
The previous version triggers on `import litellm.proxy`
Again, all according to the issue OP.