AUR adoption disabled after a second malicious commit wave

Six weeks after the Atomic Arch campaign, the Arch User Repository was hit again by the same technique, and this time the project shut the door. On July 30, 2026, Robin Candau, posting as "Antiz" for the Arch Linux DevOps team, told the distribution's mailing list that attackers were adopting neglected packages and quietly injecting malicious code through follow-up commits. Arch disabled AUR package adoption that day. On August 1 it paused AUR pushes entirely while it investigated.

The pattern was a refinement of June's. Rather than adopting a package and immediately rewriting its build script, the operators took ownership and waited, then landed the malicious change in a later commit, where it read as ordinary maintenance rather than the act of a new owner. Researchers corroborated at least 89 package names, catalogued in three batches of 27, 42, and 19, spanning security tooling, desktop utilities, and AI-themed packages. Named examples included openconnect-sso, i915-sriov-dkms, rtk-git, boringssl-git, warp-terminal-git, weather-display, and astro-box.

The openconnect-sso update was the clearest case. It introduced a binary called validator into the package build path, which executed with sudo privileges during the build. That is a step beyond the June waves, which pulled a malicious npm dependency: here the executable went directly into the build process, where AUR helpers already run with elevated privileges as a matter of course. The second stage reused the Tor-backed delivery infrastructure from Atomic Arch, which is what tied the two waves together.

Corgea's assessment was that package adoption itself now belongs in the threat model, and that once malicious content reaches the build path the trusted package name is mostly camouflage. Arch's response conceded the point. Halting adoptions removes the mechanism the attackers were using, and pausing pushes stopped the follow-up commits, but both are blunt instruments against a repository whose model assumes that users read the build scripts they run.