Loading threat actor…
Atomic Arch is a large-scale software supply chain intrusion campaign targeting Arch Linux users through the Arch User Repository (AUR). The operation abused AUR’s orphan-package adoption model to take over unmaintained packages and modify their build instructions so that package installation fetched malicious dependencies from the npm ecosystem. The campaign used multiple AUR accounts and rogue npm packages to deliver a Rust-based Linux credential-stealing payload known as deps, and it was assessed as a deliberate effort to maximize victim reach by compromising trusted packages with existing install bases. The malware focuses on developer and administrator environments. It steals SSH material, GitHub and npm credentials, browser cookies and local storage data, collaboration-platform tokens, Vault secrets, container-registry authentication data, VPN configurations, and shell histories. It also validates and enriches stolen access by querying legitimate online services using captured tokens or session material. Persistence is established through systemd services at either the system or user level depending on privileges, with runtime-generated service and executable names intended to hinder detection. A notable feature of the operation is Linux-specific stealth and post-compromise tradecraft. When sufficient privileges are available, the payload loads an eBPF-based rootkit component capable of hiding processes and network sockets from common userland monitoring tools, providing strong defense evasion on compromised hosts. The malware communicates with command infrastructure over Tor and separately uploads collected files to an external file-sharing service. Analysis also identified indications of a possible secondary Monero cryptomining staging path, although credential theft and data collection are the clearly established primary functions. Atomic Arch is best characterized as a financially motivated supply chain threat activity cluster centered on credential theft, session theft, persistence, exfiltration, and defense evasion against Linux developer ecosystems. No high-confidence attribution to a nation state or specific country of origin is currently available.
Mallory correlates actor tradecraft and target patterns against your stack, your sector, and your geography. See overlap before they land.
Who, where, and (when attributed) which flag flies behind the operation. Pulled from open-source reporting and Mallory's analyst review.
Sectors the actor has been observed targeting.
29 distinct techniques observed across reporting, grouped by tactic. Hover any cell for the evidence excerpt; click through for MITRE's full description.
1 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
Match sector + geo + tech-stack targeting against your real footprint.
Every observed MITRE ATT&CK technique, grouped by tactic.
Families this actor is known to deploy, with IOCs and behavior.
CVEs this actor has used in known campaigns.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Domains, IPs, and hashes tied to this actor, refreshed continuously.