I don’t see anything here about LiteLLM or its compromise. So, hopefully, none of the Universal Blue projects used it. And, I hope no one here got bit by this. Anyway, from:
On March 24, 2026, security researcher isfinne discovered that LiteLLM version 1.82.8—the most popular open-source LLM proxy in the Python ecosystem, with approximately 97 million monthly downloads—contained credential-stealing malware published to PyPI. Within hours, version 1.82.7 was confirmed to carry a similar payload through a different injection method. The attack was traced to TeamPCP, a threat actor conducting a coordinated multi-week supply chain campaign that had previously compromised Aqua Security’s Trivy scanner and Checkmarx’s GitHub Actions. The entire LiteLLM package has been quarantined on PyPI.
The article also contains information on who would be affected by this and how to mitigate things.
More and more of these open source supply chain attacks are happening. Here’s a Docker article talking about their recent experiences:
Since Bazzite (and other Universal Blue distributions) update automatically, is there anything in place to stop these kinds of compromised infrastructure objects from propagating up to Bazzite via their tools and then down to us in the background?
While I do not intend to speak for the Bazzite team, I know for certain that all updates for the core of Bazzite are reviewed and tested by both the team on github and automated review tools. This ensures code meets certain standards before being pushed out to users on the stable branch. The team ultimately chooses what to update and when to update after review. This greatly lowers the risk for end-users, as nothing is just pushed out as-is when things gets updated upstream; there is both time and review processes in place to catch stuff before it reaches the user.
These supply chain attacks are unlikely to affect end users of atomic systems as they are mainly targeted at developers and infrastructure using either npm or pip package management. Since (as far as I know) running npm or pip is unsupported unless in a container such as distrobox, the effect on systems running ublue os will be limited.
However, that being said, the real issue here is the cascading security issues created by these attacks. If it feels like these kind of attacks are increasing, its because they are. Each compromise leaks more API keys and developer credentials causing further compromise. Also successful attacks show a playbook for future attacks therefore leading to even more attempts.
All that being said, if you use your machine for mainly gaming or general use: you are unlikely to be affected. These campaigns are done by sophisticated groups looking at targeting large organizations through infrastructure compromise, not the average Linux desktop user. Now if you are using your machine for developer work: be very careful out there as you are in the crosshairs right now. Be on the lookout for phishing attempts even by seemingly reputable individuals. If someone tries to pressure you with urgency, that is a red flag and you should slow down and think about what information you are handing over.