[SECURITY] firefox-patch-bin, librewolf-fix-bin and zen-browser-patched-bin AUR packages contain malware - Aur-general - lists.archlinux.org
lists.archlinux.org

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.

According to the gamingonlinux discord, the following packages are also suspected to be compromised:

https://aur.archlinux.org/pkgbase/minecraft-cracked/

https://aur.archlinux.org/pkgbase/ttf-ms-fonts-all/

https://aur.archlinux.org/pkgbase/vesktop-bin-patched/

https://aur.archlinux.org/pkgbase/ttf-all-ms-fonts/

If you have any of these packages installed, immediately delete it and check your system processes for a process called systemd-initd (this is the RAT).

Here is an analysis of the malicious payload: https://www.virustotal.com/gui/file/d9f0df8da6d66aaae024bdca26a228481049595279595e96d5ec615392430d67

  • Maragato@lemmy.world
    13·
    1 day ago

    The higher the percentage of Linux usage the more likely it is that these cases will occur. Most people use Arch because of the aur repository without reading the Pkgbuilds and installing random programs from that repository that give root access to the system. Aur is a security hole in Arch and should only be used for trusted sources and programs that are widely used by the community and yet it is still a security hole for a system. When analysing this issue years ago I understood that it is better for me to have a system with a strong security configuration done by experts in the field. For me a distribution has to have these basic security tools to be considered a secure distribution: secure-boot, selinux and firewall. And along with these tools, do not install anything from external repositories. Only by fulfilling these requirements can we consider that we have a security-enforced linux distribution.