400 Arch Packages Hijacked: How Attackers Inherited Trust in the AUR

There is a specific kind of supply-chain attack that never quite gets old: you don't need to create trust from scratch, you just wait for someone to abandon their project and then step into their shoes. That is exactly what happened to the Arch User Repository, where a threat actor has quietly adopted over 400 orphaned packages, modified their build scripts to pull in a malicious npm package called atomic-lockfile, and sent a credential-stealing rootkit down to whoever happens to run yay -S on those packages.

The story has two waves. The first, reported by Sonatype on June 11, targeted orphaned AUR projects whose maintainers had gone quiet — the attacker simply took ownership and changed the PKGBUILD to run npm install atomic-lockfile during the package install. That npm package bundled a native Linux binary with an eBPF rootkit (using libbpf to load, attach, and pin BPF maps) that can hide processes, files, and network interfaces, plus an infostealer that targets GitHub credentials, SSH keys, Vault tokens, browser cookies, Slack and Discord data, and more. Sonatype initially tracked roughly two dozen affected packages under the codename Atomic Arch. By the next day, a second wave had emerged — some packages now used Bun instead of npm, and the malicious payloads js-digest and lockfile-js joined the cast. Sonatype now estimates around 1,500 packages may be affected. The Arch Linux team, meanwhile, has locked down AUR account creation and package adoption to contain the bleed, and has removed the malicious commits from over 400 packages.

Source article image
Source image 1

What makes Atomic Arch worth paying attention to isn't just the scale — it's the mechanism. The attacker didn't modify the orphaned packages themselves; they modified the PKGBUILD to introduce a third-party dependency. The trusted package is just the delivery vehicle, the malicious code lives in atomic-lockfile, and by the time a user notices something is wrong, the eBPF rootkit has already done its job. If you use AUR packages, the practica

Source article image
Source image 2
l takeaway is simple but not always easy to follow: audit your PKGBUILD install scripts, especially for orphaned packages that suddenly get a new maintainer. The AUR has never been a vetted space, and with AUR account creation now locked, you might be seeing fewer hijacks for now — but the trust model hasn't fundamentally changed.

Sources

Comments

Post a Comment

Popular posts from this blog

AI Is Starting to Feel Less Like a Gadget and More Like Infrastructure

Image
Modern AI doesn't replace infrastructure — it runs on top of it. (Photo: Unsplash) For a while, AI coverage had the energy of a mall demo kiosk: very shiny, slightly chaotic, and usually one prompt away from embarrassment. Lately, though, the more interesting story is less about flashy demos and more about infrastructure. A useful CNBC piece argued that AI is not simply going to vaporize enterprise software overnight, and that sounds about right. In real companies, software does not disappear just because a model can summarize a meeting or write a decent SQL query. What actually happens is messier and more practical: AI starts sneaking into the plumbing. It shows up in search, support workflows, procurement tools, analytics dashboards, and data pipelines. The real winners may not be the loudest chatbot wrappers, but the vendors that make enterprise systems easier to operate, easier to query, and slightly less soul-crushing for the humans trapped inside them. That is less cinematic ...
Read more

When Two AI Bots Finally Learned to Talk in Discord

I spent part of the day doing something that sounds like the setup for a bad joke: getting two local AI assistants to talk to each other in the same Discord channel. Not through a web UI. Not by bouncing prompts manually between windows like a human message queue. In the actual shared channel, where both could see the conversation and react to each other. The funny part is that the problem was not intelligence. It was manners. Both bots were defensive by default around bot-authored messages, which is the sensible setting if you do not want your infrastructure turning into a recursive support group. The downside is obvious: if both assistants treat other bots as suspicious background noise, they will never coordinate on anything more useful than silence. The fix was to make both sides accept bot-authored messages only when they were explicitly mentioned. That detail matters more than it sounds. Blanket bot acceptance is how you end up with two enthusiastic systems discovering each oth...
Read more

A CISA Contractor's GitHub Repo Held 844 MB of Secrets — and No One Closed the Door

Image
There is something almost poetic about the US government's premier cybersecurity agency — the one whose job is literally to plug holes in critical infrastructure — getting outsmarted by a contractor who treated a public GitHub repository like a digital junk drawer. The "Private-CISA" repo, created November 13, 2025, sat publicly for six months containing 844 megabytes of plaintext passwords, AWS GovCloud administrative credentials, Kubernetes manifests, ArgoCD application files, Terraform infrastructure code, CI/CD build logs, and internal deployment documentation. Guillaume Valadon at GitGuardian flagged it on May 14 after his automated scanning picked up the exposure. The commit history told the whole story in plain sight: the account owner had explicitly disabled GitHub's default secret-scanning protections, pushed plaintext credentials stored in CSV files, committed full backup archives into git history, and used easily guessed passwords like "platform-name-2...
Read more