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
You have to have some expectations and understandings of what the PKGBUILD for the package should be doing and look for something out of the ordinary. The upstream repo will usually have packaging instructions in its readme or wiki which should be reflected in the PKGBUILD.
In the case of the last incident, the attacker was adding
npmas a dependency so they could executenpm install atomic-lockfile, which was the actual attack. That was a huge red flag because most of the packages had nothing to do with JavaScript.