No. 1Score 0.83
The attack chain behind the v1.107.0 LiteLLM release
Summary and score for “The attack chain behind the v1.107.0 LiteLLM release”
LiteLLM's root-cause analysis says the malicious 1.107.0 release came from a master key committed to a public repo on May 27 and never revoked. On October 10 it yielded an org owner's GitHub token, which the attacker used to harvest two maintainers' tokens through CI. On October 21 they repointed the release workflow to a fork and approved the release with those tokens. The relaxed two-engineer approval rule helped. These details come from LiteLLM alone and were not independently verified.
Score 0.83Contestedjudges differ by 0.49 on audience breadthClaim check: 6 no source given · 2 couldn’t check
Elsewhere: HN 17 pts, front page
Score breakdown and claims for “The attack chain behind the v1.107.0 LiteLLM release”