On the 16th of July, at around 8pm UTC+2, a malicious AUR package was uploaded to the AUR. Two other malicious packages were uploaded by the same user a few hours later. These packages were installing a script coming from the same GitHub repository that was identified as a Remote Access Trojan (RAT).
The affected malicious packages are:
- librewolf-fix-bin
- firefox-patch-bin
- zen-browser-patched-bin
The Arch Linux team addressed the issue as soon as they became aware of the situation. As of today, 18th of July, at around 6pm UTC+2, the offending packages have been deleted from the AUR.
We strongly encourage users that may have installed one of these packages to remove them from their system and to take the necessary measures in order to ensure they were not compromised.
Follow up
There are more packages with this malware found.
minecraft-crackedttf-ms-fonts-allvesktop-bin-patchedttf-all-ms-fonts
What to do
If you installed any of these packages, check your running processes for one named systemd-initd (this is the RAT).
The suspicious packages have a patch from this now-inaccessible Codeberg repo: https://codeberg.org/arch_lover3/browser-patch
The Arch maintainers have been informed of all this already and are investigating.
You must log in or # to comment.
this is going to increase in frequency as linux gains popularity
This is why I felt uncomfortable when I first switched to Linux and kept reading that I didn’t need to worry about viruses as long as I didn’t click on dodgy links and only installed from trusted sources. I’m sure I’m betraying my lack of security knowledge here, but that always seemed a bit too easy.
@DirkMcCallahan @Tundra The AUR isn’t a trusted source, but most of the the Arch cult forget to mention that.
most of the the Arch cult forget to mention that
The “Arch cult’s” holy book, the ArchWiki, states the following pretty clearly:
Warning: AUR packages are user-produced content. These
PKGBUILDs are completely unofficial and have not been thoroughly vetted. Any use of the provided files is at your own risk.Mention of one’s use of the AUR for their needs doesn’t need to come with a disclaimer.
People who don’t read or don’t use their brain are going to keep not doing so, regardless.Arch is not responsible for idiots.
Arch is not recommended for idiots either. If you want cutting edge, you accept the risks. Works that way with all tech.
Half the posts on the Internet are people replying to requests for help with the message “read the wiki, the aur isn’t a trusted source, dummy”
Why do we have the AUR anyway?
To check your system for those packages (assuming you are using bash):
comm -1 -2 <(pacman -Q | awk '{print $1}' | sort) <(sort vulnerable_packages.txt)With
vulnerable_packages.txtcontaining one package name per line.We are getting to the point where inviting more people in means we will need an automated babysitter to watch for this shit and to pull it once it’s discovered. Apple has a walled garden approach that’s certainly taken a big chunk of malware threats out of their devices but their walled garden approach is ridiculous and impractical for Linux. The Microsoft method of monitoring and second guessing everything with antimalware programs is also suspect because it is super easy to abuse and resource intensive. We have clamAV but clam kinda sucks.
Linux is at the point where we need something that audits what’s going in and automatically yanks it back out remotely if it’s found to be a problem. Things can only be added by the user, but the bot can remove them without interaction of the user.
I don’t see this happening though. Instead, I see this as more of a rust vs C thing all over again, where valid critiques are drowned out by “improve your skills bro.”
Heard OpenSuse has OpenQA - apparently it is like an automatic test tool for packages.
To be fair the AUR is known to be very susceptible to that kind of thing due to the effective absence of entry requirements.
Absolutely.
The Arch User Repository is a way for anyone to easily distribite software.
Hence it has never been secure, and rather than claim it is, you mostly see people and documentation warn you about this, and to be careful if using it.
Any schmuck can make whatever they want available via the AUR. That’s how even the tiniest niche project can often be installed via the AUR. But you trade in some security for that convenience.
It shouldn’t be used as a marketplace, it should be used as a repository. You can probably find a lot of malware on GitHub, doesn’t mean you go there to choose your text editor.
I never search the AUR directly, I only use it if some README tells me I can install their software via an AUR package.
Yeah, I search the AUR not to discover packages, but to see if something I want to install is in there, if it is I check the PKGBUILD and make sure none of the sources/commands/patches are suspicious.
People need to remember it’s not some carefully vetted app store and that they need to be the ones vetting any packages they install and any changes when updating.
the firefox, zen browser and libre wolf packages are concerning. The ttf ms font too. Those are very normal apps and unless you pay attention to the package name when doing “pacman -Syu”, you would fall for the malware.
If only we can compartmentalize all AUR packages. The download AUR sources iirc are already in something like $HOME/.paru. Installing is a different story, because these packages can put their executable all over the places: /usr/local/bin, $HOME/local/bin.
With respect, you wouldn’t install these by just doing an update, so
pacman -Syuis fine.You would have needed to install these manually, or a package that depended on them - both from AUR - so you’d also need to use
yay(etc) to install them.But - I totally agree with your points that tge names look innocent enough for someone to install those over other packages.
Always look at the AUR (website) at the package details - if it’s new(ish) and has 0 or 1 votes, then be suspicious.
