Look 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:
Tell HN: Litellm 1.82.7 and 1.82.8 on PyPI are compromised
21–30 of 569 posts
Re: Tell HN: Litellm 1.82.7 and 1.82.8 on PyPI are compromised
#22good i was too lazy to bump versions
In case you missed it, according to the OP, the previous point release (1.82.7) is also compromised.
Re: Tell HN: Litellm 1.82.7 and 1.82.8 on PyPI are compromised
#23Besides main issue here, and the owners account being possibly compromised as well, there's like 170+ low quality spam comments in there. I would expect better spam detection system from GitHub. This is hardly acceptable.
i'm guessing it's accounts they have compromised with the stealer.
Re: Tell HN: Litellm 1.82.7 and 1.82.8 on PyPI are compromised
#24Seems that the GitHub account of one of the maintainers has been fully compromised. They closed the GitHub issue for this problem. And all their personal repos have been edited to say "teampcp owns BerriAI". Here's one example: https://github.com/krrishdholakia/blackjack_python/commit/8f...
Re: Tell HN: Litellm 1.82.7 and 1.82.8 on PyPI are compromised
#25Looking forward to a Veritasium video about this in the future, like the one they recently did about the xz backdoor.
Re: Tell HN: Litellm 1.82.7 and 1.82.8 on PyPI are compromised
#26[flagged]
Re: Tell HN: Litellm 1.82.7 and 1.82.8 on PyPI are compromised
#27What is happening in this issue thread? Why are there 100+ satisfied slop comments?
Attackers trying to stifle discussion, they did the same for trivy: https://github.com/aquasecurity/trivy/discussions/10420
I have created an comment to hopefully steer the discussion towards hackernews if the threat actor is stifling genuine comments in github by spamming that thread with 100's of accounts
https://github.com/BerriAI/litellm/issues/24512#issuecomment...
Re: Tell HN: Litellm 1.82.7 and 1.82.8 on PyPI are compromised
#28Thank 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 yourself for is-odd, or whatever this is, is not worth it.
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.
And even if you weren't using this specific dependency, check your deps, you might have shit like this in your requirements.txt and was merely saved by chance.
An additional note is that the dev will probably post a post-mortem, what was learned, how it was fixed, maybe downplay the thing. Ignore that, the only reasonable step after this is closing a repo, but there's no incentive to do that.
Re: Tell HN: Litellm 1.82.7 and 1.82.8 on PyPI are compromised
#29Does anyone know a good alternate project that works similarly (share multipple LLMs across a set of users)? LiteLLM has been getting worse and trying to get me to upgrade to a paid version. I also had issues with creating tokens for other users etc.
Re: Tell HN: Litellm 1.82.7 and 1.82.8 on PyPI are compromised
#30This is a brutal one. A ton of people use litellm as their gateway.