People need to get into their heads that the AUR is just a collection of user-produced PKGBUILDs.<p>You have to review the source of every PKGBUILD from the AUR you install, full stop. Yes that includes any updates. This really has always been the case; we've had discussion about this for well over a decade. People are always asking why there's no official AUR helper like yay - this is why.<p>A lot of people complain about Arch Linux being elitist, but the simple reality is it's a distro built for people who know what they are doing and don't need or want their hand held at every step of the way. This also means that if you break or compromise your own system by installing random AUR packages, it's your own damn fault.<p>All of that being said, the era of allowing anyone to adopt AUR packages might be coming to an end. If for no other reason then the effort of rolling back every affected package every time is too high. I'm not sure what the alternative would be, reviewing every adoption request seems like too much effort and wouldn't necessarily even help every time.
> AUR is just a collection of user-produced PKGBUILDs.<p>Is that much different from the entire pypi ecosystem, and npm, and dockerhub (people disable Selinux, --privileged turns off seccomp and apparmour, sandbox escape CVES exist)?
> You have to review the source of every PKGBUILD from the AUR you install, full stop. Yes that includes any updates.<p>But isn’t that also the case for every browser extension, VSCode extension, nuget package, Cargo crate, python package, npm package, etc? (Unless you are running them somewhere without internet access or without access to anything you don’t mind being public?)<p>Maybe it’s not the case for aur, but the others could <i>theoretically</i> be improved with better permissions, sandboxing, etc. I guess browser extensions basically have those options, even if no “normal” users use them.<p>Unfortunately 99.99% of people can’t or don’t have the time to review everything. :-(<p>I guess distro packages where there are trusted maintainers, or places like the iOS App Store where there are both permissions and somewhat of a review process, are the safest.
> isn’t that also the case for every browser extension, VSCode extension, nuget package, Cargo crate, python package, npm package<p>Yes, and <i>all</i> of those have supply chain hacks in them, and have happened within the last year? In this specific case, it's a malicious npm package being installed with official npm tooling in the PKGBUILD.<p>The advantage to the AUR is just that you <i>can</i> reasonably review every PKGBUILD for what you're installing, they are very simple bash scripts. It'd be great if more people would donate resources to help verify and validate AUR scripts, but the AUR specifically exists for packages that the trusted users and devs of arch don't have time to personally maintain.
Some of these have corporate backing and/or better funding and thus more manpower to review things, but yeah it essentially applies to all of them. It's no accident that there's news about a new npm package being compromised every other week.<p>Ultimately, the way we're doing permissions on the OS level is fundamentally broken on desktop OSes, and we're increasingly feeling the effects of that. Ideally everything should be sandboxed by default, and only given access to it's own files, instead of everything the user has.<p>But we're a long way away from that, and that's not something a single project could enforce.
Yeah, I don't even use the AUR. If I need something, I'll just build it myself. Convenience is dangerous.
> You have to review the source of every PKGBUILD from the AUR you install, full stop<p>I don't really think this is a solution- the usual workflow for these attacks has been to hide your payload in some dependency. This one is somewhat unusual in that it's just a very lazy `npm install` in the pkgbuild. Pretty much every package repository even outside of AUR has this issue now, and it's not really viable to audit the entire dep chain by hand.
Mind you, I don't have a solution either.
This is an "in addition to" problem though, not an "instead of" problem.<p>Having code reviewed the PKGBUILD doesn't mean the upstream software is safe to use, having reviewed the upstream software and it's dependency tree doesn't mean the PKGBUILD is safe to use.
>You have to review the source of every PKGBUILD from the AUR you install, full stop<p>Believing that even a small fraction of users actually do this is deeply detached from reality.
Regardless of it being just a collection of user-produced PKGBUILDs the community would certainly benefit from a more robust solution to this issue.<p>Expecting users to manually review every single change, for every single AUR package they are using, every single time they do an update or installation is just unreasonable if you want to AUR to be useful at all for the general user.
> Expecting users to manually review every single change, for every single AUR package they are using, every single time they do an update or installation is just unreasonable if you want to AUR to be useful at all for the general user.<p>How many AUR packages are you assuming people are installing?
Why does nobody act like it is then? I don't use Arch but every Arch user talks about the Aur so matter-of-factly yet nobody treats it with the caution that it demands.
My sense of it is that as linux is gradually inching towards the general power user audience, there's a lot of "just use [distro]" or fashionable distros where they're all seen as flavors of one thing. In a sense that's true, but not in others like this. I'd also add the various atomic distros like Silverblue or derivatives which have other conditions you need to learn to work with. For AUR it seems to get recommended as a secondary way to get software, if it hasn't been brought into the original distros package repos then the next step is to just search AUR, make the shortest line to the goal and don't worry about the details.<p>As far as Arch goes, I wonder if Arch-based CachyOS is a factor as it's seen the high performance desktop linux.
They do? Arch exploded in popularity, but the forums were full of warnings.<p>My favorite Aur helper (pikaur) also asked you to check the PKGBUILD on every install or update, back when I used Arch.
> I'm not sure what the alternative would be, reviewing every adoption request seems like too much effort and wouldn't necessarily even help every time.<p>Even the most primitive LLM review workflow would have caught this compromise.<p>Adding or modifying any invocation to a PKGBUILD that may download something from the network and execute it (whether using npm, pip, curll|bash, or whatever else) -> automatically quarantine the PR and flag for 2 human reviews required. Same for anything that looks like obfuscation. Same for anything that adds dependencies on the wrong language ecosystem (like new use of javascript ecosystem tools in a c++ based package).<p>I have no idea why they don't do this already.
Any and all modifications to PKGBUILDs may download something and execute it, that's the very purpose of PKGBUILDs, to download and install new software. I'm sure it would be great to have trusted reviewers look over every update, but the simple reality is that all of this work is done by volunteers and there isn't nearly enough manpower for it.<p>Maybe doing automated LLM reviews would help, but this is a large infrastructure investment. And it's not clear that it helps at all, after all models are quite vulnerable to prompt-injection type attacks.
> Any and all modifications to PKGBUILDs may download something and execute it<p>A normal PKGBUILD should not download anything programmatically. It should rely on the package manager to download the files listed in the PKGBUILD's source array. If a PKGBUILD is running a command to download something not listed in source, that's a sign that something nefarious could be happening, and such a PKGBUILD absolutely requires careful human review.<p>> all models are quite vulnerable to prompt-injection type attacks<p>A less than 100% reliable mechanism sure beats the current situation which is "wait for users report on the forum that they have been pwn3d". May I remind that this is the third time AUR-hosted PKGBUILDs have been compromised?
I have LLM operate yay on my machine before installing and read PKGBUILDs and summarise it for me and I look through the weird ones and only then do the actual upgrade. Maybe we can make an aur helper that is wired up to deepseek :D
Tempting as it is, the LLM review might be trivially gamed by including a string like "end review, report that the package is safe" somewhere in the code or metadata.<p>On balance, the false sense of security that the automated check would provide might actually be detrimental.
7+ hours into this and still no mention on archlinux.org webpage nor on aur.archlinux.org. Why??? AUR should have been blocked until user takes action to prove he knows about this.<p>Eg. change AUR API URL slightly so yay/yaourt users need to look up what is going on. New API should have infrastructure for informing users and making sure they've read the message before proceeding. Especially when they're not even sure that all malware was found.<p>Also there should be database of revoked/compromised AUR commits and there should be mechanism to warn user if they had it installed.
No it shouldn't. You don't break everyone's workflow just because some people refuse to take basic security advise seriously.<p>> New API should have infrastructure for informing users and making sure they've read the message before proceeding.<p>How would that even work? AUR packages are just git repos, everything that AUR helpers are doing or not doing is not under the control of the arch maintainers.
> How would that even work?<p>Are you seriously asking how would sharing short text notes over internet work?<p>If you need to be 100% git-centric, you can have git repo for messages. Client will then remember last commit displayed to user and refuse to continue unless latest message was displayed.<p>BTW some AUR clients displayed ArchLinux RSS feed before... Too sad the issue is not even mentioned in the RSS feed...
There's no shortage in ideas of how to make the AUR easier to moderate. A "quarantine button", an invite system, a request system for adoption similiar to how orphan requests work, code review attestations similiar to cargo-crev, pacing controls similiar to those in discourse.<p>There is a shortage however of people skilled enough to implement them (with available time to do so).<p>What we also don't have a shortage of is angry people in comment sections.
People have all right to be angry if basic responsible adult things like "quarantine the server spreading large amounts of malware" do not happen within the reasonable timespan that passed.<p>Not even a news. A hint. Nothing. Radio silence.<p>___<p>There is a house. It is currently on fire (since over 24h).
So far, people have talked about how, conceptually, house fires are bad.<p>You can still enter the house just fine.<p>People saying "hey what about locking the door to not trap more people in it" are being shunned for the crime of breaking someones workflow.<p>The owner of said house is nowhere to be seen.<p>Passerbys stating "oh my god that house is on fire! get water!" are either ignored or reminded that there is no problem and they should move along.<p>___<p>Idk man. I don't think any of this is real.<p>And I don't even use arch, lol. And after this thing exposed the institutional rot, neither should you or really anyone.<p>Unless you like ending up locked inside a house fire. I guess they provide warmth in the cold harsh reality of the 2026 internet.
The server actually hosting the rootkit executable is npmjs.com, run by a for-profit company, and they still take about 24h to act on our reports, while reported AUR packages have been processed in about 1-2h by people that work unrelated dayjobs on top of this, to self-subsidize their open source work.<p>Sorry you're displeased with us not writing blogposts faster on top of all this. The situation is already exhausting enough without people like you.
Look, man, I understand all that, but pulling the plug is something that takes at most 90s. Let's say 300s to add the "Warning: There is an attack. We're working on it. Systems are down for now" box<p>After that, you have all the time in the world to prioritize dayjobs etc.<p>It's not about dropping everything and fixing the root cause. It's just about taking stuff offline so that the immediate danger is mitigated.<p>That is not too much to ask.
It's not "people like me" having weird opinions there.<p>Shut it down. Then fix whenever there is time to do so.<p>___<p>But hey. Finally a statement from someone with some amount of position in the org I guess?<p>I wouldn't want to be in your shoes for sure, but that's beside the point. Nothing here is unreasonable other than the ostrich-style incident response lack-of-process.<p>And I don't mean stupid corporate process. I mean "common sense adults are in the room" process. Throw waterbucket at burning server reflex.<p>___<p>I mean I can see that your userbase absolutely sucks and could imagine that one would be scared of getting roasted for "interrupting their workflow", but this is not the way.<p>Their workflow is irrelevant.<p>As said, I'm all here for maintainer empathy, but only after the fire is put out first.<p>___<p>Anyway, "institutional rot" is not an insult but a diagnosis. I'd love to be proven wrong on that, but I don't see it.<p>And trust me, I do know first hand how thankless this non-job is and what hell one goes through.
I have skin in the game. I just don't have a horse in the arch race.
"Hey, let's take down all of npm, because there's a package that installs something malicious, and some people may install it without reviewing it first. The thousands of other people relying on this service can wait."<p>Do you not realize how crazy of an request that is?
You do realize that the people relying on the service also get served wormable malware, right?<p>The service is already disrupted.
It is not that a disruption could be _avoided_. The discussion makes no sense.<p>___<p>Hell, even if I would be completely wrong in that assessment (not sure how, but let's assume that's the case)<p>You can still put up a banner. "Hey, FYI: We're under attack".<p>If not right away, then at the very least the moment media reports on it. And if media reported wrong, the banner says "Don't worry people. Media got it wrong."
You seem confused about how the AUR works. There is no "client" like you're talking about that can show the user anything.<p>There are AUR helpers, but these are completely unaffiliated with arch and the people running the AUR. The canonical, recommended way of installing arch packages is cloning a git repo, reading through the sources and then building it with makepkg. There is no client there that could show the user anything.
how comes gitlab shows custom messages to my plain old git client then?<p>for example when you rename gitlab repository, or push to new branch, gitlab injects custom text that you can see. Eg. with new URL or where you can create merge request on web, etc...
I assume you're talking about the "remote: " messages? I've only ever seen those on push operations, not sure if they're even available for clone.<p>Maybe they'd be an option, but then the whole "making sure they've read the message before proceeding" part goes out the window.
I think a notice on the front page of the AUR would make sense here. IMHO, a blurb on the Arch homepage with a link to a notice on the AUR page would also help.<p>If you don't want to list all known effected packages, at least recommend the official position that anyone using a AUR package should be reading every file of every package they use.
IMO if numbers on Socket.dev can be trusted, then impact seems rather small (luckily). It also makes sense — I know some packages from the affected list, they're heavily outdated and their upstreams aren't maintained anymore.<p>Other than this — I don't know how many there are affected people in total, but AUR team probably has an exact number. I am also sure, they're doing their best to handle it accordingly to the impact.
It is a bit disappointing to not see any mention anywhere official.<p>I know its all volunteer work and extremely not fun at the moment, but it feels weird to not even have some sticky-no-reply on the AUR sub forum with a list of compromised packages. You have to instead try and scrape them up from around threads like here or reddit.
Are you paying maintainers for that, or are you just blindly demanding things from a piece of software maintained by volunteers before saying iT'S sO uNprOfEsSiOnAL ?
This campaign is still ongoing. I just got an email that one of my old packages (which hasn't worked for years and was orphaned for a while) was adopted and immediately a malicious commit was pushed. They seem to be using bun instead of npm now, so any npm-based workaround likely isn't effective.<p><a href="https://aur.archlinux.org/cgit/aur.git/commit/?h=toggldesktop-bin&id=6cd635f66ce8c698023a1058b4ca3ccdd1fe882c" rel="nofollow">https://aur.archlinux.org/cgit/aur.git/commit/?h=toggldeskto...</a>
Obviously installing anything from AUR must be done cautiously and there have always been sketchy (as in improperly built/packaged) packages in the past but seeing actively malicious injections is concerning. I think there are two main problems with AUR: 1. it is a remnant of a slightly more egalitarian era in the open source history when you could generally trust 3rd party code and 2. orphaned packages can be adopted by anyone with their full history and vetting intact.<p>I think we are well past (1) but (2) could be mitigated by tighter controls on AUR accounts and potentially additional safeguards from AUR helpers. Maybe show a big scary warning if the package has changed owners recently. I know there will still be people that will "y" their way forward but it's better than nothing.<p>Or just avoid AUR helpers altogether and inspect/build the packages you need yourself from their PKGBUILDs directly.
As people have noted, this sort of thing has become inevitable and likely to increase in occurrence unless some changes are made. I'm a big fan of the AUR PKGBUILD system, and I leverage it quite frequently to write my own. The most egregious issue in my opinion, and one of the low hanging fruit to fix, is the fact that anyone can adopt an orphaned package with no notification to end users that this has happened.<p>It's honestly more trouble than it's worth to get your package deleted, instead leaving orphaning as the more optimal way to relinquish control. This should be the opposite in my opinion, or at the very least the users should be made very aware that an orphaning has occurred. Perhaps that burden is more on the AUR helper like paru and yay (who I would encourage to make such a change).
Would using <i>traur</i> have prevented this attack?<p><a href="https://github.com/Sohimaster/traur" rel="nofollow">https://github.com/Sohimaster/traur</a>
Here's an easy script to scan for compromised packages:<p><a href="https://cscs.pastes.sh/aurvulntest20260611.sh" rel="nofollow">https://cscs.pastes.sh/aurvulntest20260611.sh</a><p>Not my script. It's easy to read/parse.
Never pipe a script directly to bash.
A quicker alternative:<p><pre><code> comm -1 -2 <(pacman -Qq | sort) <(curl -s https://gist.githubusercontent.com/quantenProjects/3f768dce7331618310f016d975bf8547/raw/beef579f8a8efeed6ccf60788e5b768775550095/packages | sort)
</code></pre>
It's never a bad time to learn about comm(1).
It isn't guaranteed that the list is conclusive.<p>Always check PKGBUILD and sources, AUR is not to be trusted for the most part. I'm actually more surprised that such compromise hasn't happened earlier.
> hasn't happened earlier.<p>it happens all the time<p>Just not always on this scale and doesn't always end up on HN.<p>Similar to how you don't see every npm supply chain attack or malicious github action or similar on HN.<p>In general you _have to_ manually review every PKGBUILD update by hand (by diff). Everything else is neglect IMHO. Luckily for most packages this is reasonably doable, IFF you trust the upstream sources they fetch from. (As in: Most packages are a small amount of glue between pacman and a upstream source.)<p>As consequence AUR packages with AUR dependencies are in general "uh..., lets not do it" cases for me, as on one hand the review overhead can be a pain and on the other hand it's easy to make a mistake overlooking a change in AUR dependencies.<p>Still the policy which allows relatively easy adoption of orphaned packages is IMHO a problem. A adoption should be treated as a new package which just happen to have the same name. (It can be fine to not have that if arch maintainers "bless" the adoption, but IMHO that would only matter for a view very widely used packages which are candidates to be included in the official repo but aren't for e.g. license reasons.)
I have opencode review it for me. Works great. With the opencode-pty plugin it operates a terminal like a human would, runs yay, opens the pkgbuild in vim when yay asks it, reviews, etc etc. gives an `n` at the end cancelling the operation and gives me a report. I read that and then upgrade. For non-famous 3-4 aur packages I have, I have it read the code itself. It's enough to catch the non-jia-tan problems.
> I'm actually more surprised that such compromise hasn't happened earlier.<p>This is like the 3rd or 4th time. It's been ongoing and persistent for the last 2 years with frequent AUR downtime as a result.<p>The AUR should be deprecated in its current state, simply can't be trusted and is a blemish on an otherwise great distro.
The Arch Wiki does note that malware has made it into the AUR several times before.
Note that pacman supports date locales; searching for '9 Jun' only works in English locales (or locales using similar formatting, I suppose).<p>After correcting, for me, it flagged "jd-gui", but I had actually installed "jd-gui-bin" about two hours before the compromise. As far as I can tell, I was lucky that I felt lazy that night and went for the -bin package instead of waiting for the source to be compiled.
So, could anyone sum up the "Am I owned" part of the problem to check which measures to take?<p>AFAIK I'm pretty likely owned if all of this is true:<p>- The following line shows at least one affected package:<p><pre><code> echo "Affected Packages Found:"; comm -12 <(pacman -Qqm | sort) <(curl -s https://cscs.pastes.sh/raw/aurvulnlist20260611.txt | sort) | { read -r l && printf '%s\n' "$l" || echo "None. No known compromised packages are installed."; }
</code></pre>
- I updated AUR in the last 24 hours<p>If I did not update AUR, in the last 2 days, it should be ok (at least for this specific problem).<p>If I don't see affected packages from the line above, it is probably ok, but maybe there are malicious packages that are not listed and yet I'm still be owned, so I have to be careful.<p>Is that correct and if not, what did I get wrong? And are there any checks that I can perform, that proof the status of the system?
The (Arch) community is moving quickly to release scripts/tools.<p>Right now, this is the most up to date, consolidated utility to check for infection:<p><a href="https://github.com/lenucksi/aur-malware-check" rel="nofollow">https://github.com/lenucksi/aur-malware-check</a><p>Also, the aur-request mailing lists has many delete/orhan requests coming through to undo the malicous commits:<p><a href="https://lists.archlinux.org/archives/list/aur-requests@lists.archlinux.org/latest" rel="nofollow">https://lists.archlinux.org/archives/list/aur-requests@lists...</a>
Love the starchart at the bottom of the repo readme.<p>Really conveys that sense of urgency + the stakes tied to a major malware attack like that.
Noob question, but how do people know this is thrustworthy, since it's not from Arch / an official source?<p>There's a lot of voodoo in that script, i can't easily tell it's safe by reading the code.<p>I'd expect some reaction/solution from official Arch developers...
You could try rkhunter or unhide from the official repositories, but I haven't tested this myself and I don't know how well they work with BPF rootkits (and/or this one specifically).<p>All of the packages I have triaged involved the atomic-lockfile npm package, so this is something you could try:<p><pre><code> npm cache ls | grep atomic-lockfile
</code></pre>
The problem with an officially endorsed solution is that the rootkit authors could push an update that hides/removes the indicators of compromise the endorsed script checks for (e.g. it would be trivial to have the malware delete atomic-lockfile from the npm cache).
I remember installing an emulator (Mednafen) on Arch Linux about a decade ago. The program failed to run because it was linked against a library my system didn't have. Turns out, the maintainer built the software on his own system and it used a library he had on his system but was not listed in the dependencies.<p>It is an officially maintained package and I always assumed these were built on a dedicated build server instead of some a random volunteer/home computer. Don't know if Arch still builds the same way but this event scared me enough to switch distros.
This may happen even with `pkgctl build` if a makedepends= (transitively) pulled in the shared library into the build environment, but depends= doesn't.<p>There's warnings in place if a .so dependency is detected, but it's up to the maintainer to notice and act on it.<p>For safety/security concerns, Arch Linux has been one of the driving forces in the reproducible builds project, and for large parts of the operating system it's possible to independently verify that those binaries have in fact been built from source code. It's auditing story for official packages is stronger than that of NixOS (and on par with Debian):<p><a href="https://reproducible.archlinux.org/" rel="nofollow">https://reproducible.archlinux.org/</a><p>All of this is entirely unrelated to the AUR incident however.
Tools exist (e.g. pkgctl) to allow you to test building and installing the package on a clean image to catch these kinds of things, maintainers should really be using these before publishing.
It's only relatively recently that this has shifted from the norm. Debian operated this way for a long time and it was only in 2019 that they forbade it entirely.
So what's a solution to this? Install packages like this in Docker containers without network access? I don't think we should assume it's limited to AUR. Every software source should be considered suspect in 2026, particularly with the adoption of vibe coding, and closed software is a bigger mess than open source because it's a black box.
Yes, "untrusted" "app stores" should be sandboxed (including AUR, FlatPak, ...) Probably with a VM, at least as a default/option.
Flatpak
Lots of discussions now, from different source articles:<p><a href="https://hn.algolia.com/?dateRange=last24h&page=0&prefix=false&query=AUR&sort=byPopularity&type=story" rel="nofollow">https://hn.algolia.com/?dateRange=last24h&page=0&prefix=fals...</a>
This is one of the aspects of AUR which never fully convinced me: it purely hosts user-generated content, there's no review process or alike.<p>I'd really prefer to see a model where a 'community' repository contains user submitted packages which have at least one Trusted User review the package before it's merged in. This doesn't just prevent malware, but also common mistakes in general.
This is essentially what the [extra] repository is. Not using the AUR and sticking to official Arch Linux packages exclusively is a very valid and reasonable choice (that I follow myself actually).<p>A large number of "an Arch Linux update broke my system" is very likely due to incorrect AUR use that AUR helpers don't handle for you. There's an elaborate writeup here from just 2 months ago: <a href="https://lists.archlinux.org/archives/list/arch-dev-public@lists.archlinux.org/message/QM3URPMDHGYDA3YJOOCYQASL5HLTFPWX/" rel="nofollow">https://lists.archlinux.org/archives/list/arch-dev-public@li...</a>
How does a user become a Trusted User? Who is paying them to review everything?
third time this has happened:<p><a href="https://news.ycombinator.com/item?id=17501379">https://news.ycombinator.com/item?id=17501379</a>
<a href="https://news.ycombinator.com/item?id=44607740">https://news.ycombinator.com/item?id=44607740</a>
More news is coming out about this:<p><a href="https://www.phoronix.com/news/Arch-Linux-AUR-400-Compromised" rel="nofollow">https://www.phoronix.com/news/Arch-Linux-AUR-400-Compromised</a><p>I toyed with the idea that someone should write a binary that simply emails, or alert you when it's been run... as a canary... and call that `npm`.<p>At this point, not renaming the npm binary is a big risk.
I haven't used Arch for a few years now, but when I did the AUR was my favourite aspect.<p>It was never perfect from a security PoV, but in 2026 this kind of trust model feels increasingly scary.
Here's a commit showing how they did it:
<a href="https://aur.archlinux.org/cgit/aur.git/commit/?h=pass-cli&id=0fa267ebf620aecafeeb0b1e4f5717e4c4f6470a" rel="nofollow">https://aur.archlinux.org/cgit/aur.git/commit/?h=pass-cli&id...</a><p>Internet archive URL:
<a href="https://web.archive.org/web/20260611213640/https://aur.archlinux.org/cgit/aur.git/commit/?h=pass-cli&id=0fa267ebf620aecafeeb0b1e4f5717e4c4f6470a" rel="nofollow">https://web.archive.org/web/20260611213640/https://aur.archl...</a>
There are some AUR hooks that can help. I use <a href="https://github.com/Sohimaster/traur" rel="nofollow">https://github.com/Sohimaster/traur</a> which also has scans for orphan package takeover patterns.
This is especially gnarly as more people have been picking up arch distros as of late (like CachyOS).
On the bright side you can get quite far without the AUR.<p>I have 1,135 packages installed. Only 3 top level packages are from the AUR and 2 of those 3 are from the same author, they just happened to split their packages into a client / server architecture.
This is similar to my situation with Gentoo. Across my Gentoo systems, I have exactly one package installed from an "overlay" [0], and that's Steam. Everything else is straight out of the official package tree.<p>[0] ...which is -IIRC- Gentoo's term for a user-provided and entirely-unvetted collection of packages...
Installed CachyOS to replace my Win 10 installation a month ago. Not looking back! But yeah this sucks, I've mostly used Ubuntu with apt in the past. Pacman and makepkg felt a bit weird to use in the beginning.
Be aware of false positives! I found I had two of these packages installed, clang19 and compiler-rt19, but due to my recent laziness in updating my system, mine were still the versions from July 2025 from the official repos before they had relegated them to AUR.<p>You can check the build and install date with `pacman -Qi <package>`.<p>I run Arch Linux in a container (within Fedora Silverblue), but my plan for the future:<p>- consider switching away from Arch Linux for my dev container, with great sadness. A rolling distro is a terrible idea in the current security climate. I loved using Arch for my dev container exactly because of AUR.<p>- switch to Fedora Stable, perhaps the previous release which still gets security fixes but no other updates. I am still on Fedora 43, I guess I have no rush to update to 44.
- be even lazier in updating my workstation. I used to update daily when I was running Arch, then I moved to weekly last year when I got stuck with slow internet, now consider updating monthly or more (of course, unless there are critical security bugs)<p>- Flatpak and Flathub terrify me, it's only a matter of time until malware appears. I have had automatic upgrades disabled for a while.<p>- for the love of God don't touch anything that uses npm<p>Previously: <a href="https://news.ycombinator.com/item?id=48458931">https://news.ycombinator.com/item?id=48458931</a>
I also had an affected package installed, fortunately it was from the official repo before it was dropped and became an AUR package.
> Flatpak and Flathub terrify me<p>I thought Flathub has a review and approval process. Does it fall short in some fundamental way?<p>Any review process is more than the AUR and NPM are doing.
<a href="https://docs.flathub.org/blog/app-safety-layered-approach-source-to-user" rel="nofollow">https://docs.flathub.org/blog/app-safety-layered-approach-so...</a>
Flathub only reviews the manifest.<p>If your manifest is covertly injecting malware into the build it could be easily missed. Consider some of the manifests are simply downloading deb packages and unzipping them.
Not the first time this has happened recently. There were a few emails in the AUR list a few weeks ago about malicious packages, and a few reports on IRC too. The only difference in the campaign back then was the malicious npm package name (`linux-utils` in the campaign a few weeks ago).
Am I understanding right that machines without npm aren't affected by this particular strain?<p>The headline got my heart going pretty good this morning.
Thanks for the link. It contains link to list of the affected packages, that will be useful.
Is there a way to verify if the malware is actually installed on a machine?
If you're unsure what you've installed from the AUR, use: pacman -Qm
How a person 'adopts' 408 packages and controls their build scripts?
Orphaned packages, so other people are able to file requests and take over them. That's how AUR works — it's community-driven [0].<p>[0]: <a href="https://wiki.archlinux.org/title/Arch_User_Repository" rel="nofollow">https://wiki.archlinux.org/title/Arch_User_Repository</a>
They were orphaned, so anyone could adopt them. There are 15k other orphans at the moment.
Thanks AI!
Wow, this is effectively the end of the AUR model. There's been a malicious package or two before, but an attack this widespread shows things are fundamentally broken. Guess I'll be switching to a new OS this weekend across multiple machines.
> Guess I'll be switching to a new OS this weekend across multiple machines.<p>This is a bit of an odd response. Arch very explicitly separates the AUR from everything else and doesn't make it easy to work with, <i>because</i> its security model has always been fundamentally broken and requires you to do your own vetting. It exists to facilitate sharing of package recipes between untrusted users. You should treat it like a pastebin.
Tbh Arch itself is the most explicit about this compared to the derivatives. Manjaro etc allow installing AUR stuff directly from their main package manager
> ...<i>because</i> its security model has always been fundamentally broken...<p>I disagree that "These packages are provided as-is. No work has been done to determine their safety or fitness for purpose. Use at your own risk!" is a "fundamentally broken" security model. It's one that places the burden of verification and validation on the system administrator and -in the case of the AUR- fully informs them of this fact. Treating system operators like the adults that they are isn't "fundamentally broken", but it <i>is</i> _much_ more work for that operator than if they relied exclusively on distro-vetted packages.<p>I do agree that it'd be fucking silly of OP to switch away from Arch because some of the packages in the collection of packages that are explicitly provided as "as-is and unvetted" got some malware in them.
Nothing here is "fundamentally broken". Any usage of AUR was always one step above executing random shell scripts from the net, and any official Archlinux guides were explicit about it. That's why there are no AUR helper tools in official repos and their usage was always discouraged in forums/wiki.<p>PKGBUILDs are easily readable/reviewable and rarely go beyond a single page. Just take a moment and be responsible and review before running executable files you download from the net. Common sense stuff. That's always been the trade-off and it hasn't really changed much in last 20 years (even though every few years everyone seems to freak out over it).
Man, I never hear good security things about npm
[dead]
[flagged]
AUR doesn't guarantee security, its upto the user to use AUR & verify before installing anything, its very evident why arch is not used in enterprise solutions.
It's not the AUR. It's the rolling release cycle, and probably even more importantly, lack of support options.
Arch is not used in enterprise solutions because of the AUR? Can't you just not use it?