Update: the Arch Linux AUR supply chain attack just got much worse.
When I posted earlier, around 400 packages were compromised.
Now it's reportedly over 1,500.
The malware isn't just stealing credentials.
It's targeting developers by harvesting:
• SSH keys
• GitHub tokens
• npm credentials
• Browser sessions
• Slack, Discord & Teams accounts
• VPN configurations
And on privileged systems, it can reportedly deploy an eBPF rootkit to hide from security tools.
This is quickly becoming one of the largest AUR compromises ever seen.
If you're an Arch user, now would be a good time to audit your recent AUR installs.
Over 400 Arch Linux AUR packages were just compromised.
And this is a reminder that open source doesn't automatically mean secure.
Attackers reportedly hijacked package maintenance and injected malware capable of:
• Stealing GitHub credentials
• Extracting SSH keys
• Harvesting browser cookies
• Accessing Slack, Discord & Teams data
• Collecting VPN credentials
• Deploying an eBPF rootkit
The scary part?
Many developers install AUR packages without reviewing every PKGBUILD.
Affected systems may have exposed:
• GitHub tokens
• npm credentials
• Docker & Podman secrets
• HashiCorp Vault tokens
• SSH artifacts
• Browser session data
If you're running Arch or an Arch-based distro and recently installed AUR packages:
• Audit installed packages
• Check for indicators of compromise
• Rotate credentials immediately
• Consider a clean reinstall if rootkit activity is suspected
This isn't an Arch Linux problem.
It's a software supply chain problem.
One compromised package can put thousands of developer machines at risk.
Do you review PKGBUILDs before installing AUR packages, or do you trust the community by default?