Skip to content
Tech News
← Back to articles

Arch Linux disables AUR package adoption to stop malware flood

read original more articles
Why This Matters

The temporary disabling of AUR package adoption by Arch Linux highlights the growing threat of malware and malicious package hijacking in open-source ecosystems. This move underscores the importance of security vigilance for both developers and users in the Linux community, as malicious actors increasingly exploit package repositories to distribute malware. Addressing these threats is crucial for maintaining trust and integrity in open-source software distribution.

Key Takeaways

The Arch Linux project has temporarily disabled adoption of Arch User Repository (AUR) packages after a surge in malicious takeovers of existing packages.

The decision was announced on the distribution's mailing list by contributor Robin Candau, who said that the situation is temporary until a solution is found.

“Due to the current influx of malicious package adoptions and follow-up commits made via the AUR, package adoption is currently disabled while we are handling the situation,” announced Candau.

“We will send a follow-up once we're able to. In the meantime, feel free to report suspicious adoption events or commits that haven't been dealt with yet, and stay vigilant!”

Independent Federated Intelligence Network (IFIN) conducted a technical analysis of the malware and reported that the campaign began on July 29 with the package ‘openconnect-sso.’

IFIN reports that the campaign bears many similarities to the last campaign, including the use of the Tor network for staging.

In June, a separate campaign hit AUR via more than 400 packages, distributing a Linux rootkit and info-stealer malware to unsuspecting users.

In the latest attack, the researchers identified a two-stage infection, with the first stage acting as the loader, and the second one being a Linux x86_64 payload described as stealer malware with remote administration (RAT) and SSH worm features.

Further analysis showed that the first-stage loader evades detection by checking for debuggers, sandboxes, virtual machines, and CI/CD environments before installing systemd services and cron jobs to ensure persistence.

It then downloads and launches a Tor client disguised as dbus-daemon to retrieve the second-stage payload from an ‘.onion’ server.

... continue reading