this post was submitted on 26 Jul 2026
14 points (81.8% liked)
Arch Linux
9878 readers
1 users here now
The beloved lightweight distro
founded 6 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Those headlines were the usual "mention (seemingly) big numbers without context"-bullshit. You can easily look up the actual amount of packages in the AUR...
They also did not "inject malicious code into AUR packages" because of some insecurity that needed fixing. They simply took over orphaned packages then modified them.
So actual reality boils down to:malicious actors took over a miniscule amount of AUR packages with so little public interest nobody even maintained them. And the AUR is as secure as it ever was. Which means not very secure at all because it's public community content without any vetting. So look up the package and actually read the PKGFILE. Just as Arch is vocally warning you.
99.9% of changes are version numbering, checksum and rarely slight dependency changes. There is no chance anyone affected by a long orphaned package that got taken over and modified did ever read that one stupid file of just a few lines (or just the dif provided by several AUR helpers automatically).
I agree, but I wanted to clarify this point for anyone: they didn't "take over orphaned packages" themselves, they took over the install processes, provided by the AUR for packages, that have likely been abandoned by the maintainers. The AUR doesn't host the actual code for software itself; it's just a set of instructions that tells the client where to grab code from and what to do with it.