Skip to content
supplychainattack.orgSupply chain attack incident catalog
containedhigh

400+ AUR Packages Hijacked: What the “Atomic Arch” Campaign Means for Supply-Chain Security

On June 11, 2026, attackers hijacked over 400 packages in the Arch User Repository (AUR), converting them into a malware delivery network. The "Atomic Arch" campaign represents a large-scale compromise of developer accounts or package maintainers within the Arch Linux ecosystem.

ShareXLinkedInHacker News
Disclosed
Last updated
Blast radius
400+ AUR packages; limited to Arch Linux systems
Ecosystems
Attack vectors
Threat actor
Affected entities
  • Arch User Repository (AUR)400+ community packages hijacked

On June 11, 2026, security researchers and the Arch Linux community disclosed a large-scale supply-chain attack targeting the Arch User Repository (AUR). Attackers successfully hijacked more than 400 community-maintained packages and repurposed them as a malware distribution channel.

The campaign, referred to as "Atomic Arch," demonstrates how modern attackers exploit trust relationships within open-source ecosystems. The attack likely involved compromise of developer accounts or package maintainers, allowing unauthorized modification and distribution of malicious code through legitimate package channels.

While the immediate impact is confined to Arch Linux systems, the incident underscores systemic vulnerabilities in community-driven package repositories where maintainer account security and package integrity verification may be insufficient to prevent large-scale takeovers.

Remediation

  • Audit AUR account credentials and enable multi-factor authentication for all package maintainers
  • Review and revoke compromised package versions; restore from known-good sources
  • Implement mandatory code review and signing requirements for package updates
  • Monitor Arch Linux systems for indicators of compromise from malicious package installations
  • Conduct forensic analysis to determine attack vector and scope of account compromise

Sources

  1. 400+ AUR Packages Hijacked: What the “Atomic Arch” Campaign Means for Supply-Chain Security · StepSecurity

Cite this entry

"400+ AUR Packages Hijacked: What the “Atomic Arch” Campaign Means for Supply-Chain Security." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed June 11, 2026; last updated June 13, 2026. https://supplychainattack.org/incident/400-aur-packages-hijacked-what-the-atomic-arch-campaign-means-for-supply-chain-s-ar2fhv

Suggest a correction

Found an error or have a newer source? Corrections to factual errors take priority over new entries.

  1. activecritical

    The Worm That Keeps on Digging: TeamPCP Hits @antv in Latest Wave

    TeamPCP conducted a multi-ecosystem supply chain compromise targeting the @antv package and associated development infrastructure. The attack leveraged GitHub, NPM, and VSCode to steal credentials and establish persistence mechanisms.

    TeamPCPnpmOtherAccount takeoverCompromised packageMalicious maintainer
  2. containedcritical

    Malicious code in jest-canvas-mock (npm)

    The npm account `atool` was compromised and used to publish 631 malicious versions across 314 npm packages, including jest-canvas-mock, in an automated 22-minute burst. Each malicious version injects a preinstall hook executing an obfuscated Bun script that exfiltrates credentials and establishes persistence via CI/CD workflow injection and system daemons.

    Mini Shai HuludTeamPCPnpmOtherAccount takeoverCompromised packageMalicious commit
  3. containedcritical

    Malicious code in mcp-mermaid (npm)

    The npm account `atool` was compromised and used to publish 631 malicious versions across 314 npm packages, including mcp-mermaid, in an automated 22-minute burst. Each malicious version injects a preinstall hook executing an obfuscated Bun script that exfiltrates credentials and establishes persistence via CI/CD workflow injection and system daemons.

    Mini Shai HuludTeamPCPnpmOtherAccount takeoverCompromised packageMalicious commit
  4. containedcritical

    Malicious code in @antv/li-editor (npm)

    A threat actor compromised the npm account `atool` and published 631 malicious versions across 314 npm packages, including @antv/li-editor, in an automated 22-minute burst. Each malicious version injects a preinstall hook executing an obfuscated Bun script that exfiltrates credentials and establishes persistence via CI/CD workflow injection and system daemons.

    Mini Shai HuludnpmOtherAccount takeoverCompromised packageMalicious commit