Re:Tell HN: Litellm 1.82.7 and 1.82.8 on PyPI are compromised
by bonoboTP on Wednesday March 25, 2026 @11:53AM
(#47519072)
You don't have to outrun the bear, just the other guy.
Re:Tell HN: Litellm 1.82.7 and 1.82.8 on PyPI are compromised
by zar1048576 on Thursday March 26, 2026 @07:22PM
(#47537145)
Wouldn't this just be a case of the bear catching one guy and then catching the other guy (especially if the issue was unnoticed altogether after the set number of days)?
Re:Tell HN: Litellm 1.82.7 and 1.82.8 on PyPI are compromised
by talkin on Wednesday March 25, 2026 @02:37PM
(#47521393)
There will always be early adopters.
And maybe more importantly: security tools and researchers.
Re:Tell HN: Litellm 1.82.7 and 1.82.8 on PyPI are compromised
by zar1048576 on Thursday March 26, 2026 @07:21PM
(#47537134)
The minimum-release-age heuristic is certainly helpful as it theoretically gives the community a chance to identify the issue. Of course, in practice, these things aren't scanned or analyzed the way they should ideally be, which is a deeper issue. Pinning has definitely saved me on more than one occasion, but it doesn't strike at the root of the issue.
Next up, we're going to advise a minimum-release-age of 14 days, cause most other projects use 7 days.