js-digest
Techniques & procedures
17 distinct techniques documented for this family, organized by ATT&CK tactic.
Initial Access
3 techniques
Initial Access
The Arch User Repository (AUR) suspended new registrations Monday due to an ongoing supply chain attack flooding the repository with more than 1,500 malicious packages.
The attackers injected commands into build scripts that pulled malicious dependencies, including rogue npm packages such as atomic-lockfile and js-digest, which executed automatically during the package build process.
This attack goes after the trust model, not a software flaw. The compromised packages kept their names, their histories, and the trust that came with them. Only the build instructions changed.
Execution
5 techniques
Execution
In an initial wave affecting about 400 packages, this script executed an npm install command for a package called atomic-lockfile. Shortly afterward, the attackers switched tactics, instead using the Bun runtime to install packages called js-digest and lockfile-js
atomic-lockfile ‘s package.json contains a preinstall lifecycle hook: "preinstall": "./src/hooks/deps"
A user runs their AUR helper ( yay , paru , or raw makepkg ) to install or update a package.
the attack began Thursday when attackers abused AUR’s stewardship process for adopting orphaned packages to claim ownership of abandoned, legitimate packages and modify them with malicious PKGBUILD post-install scripts.
После получения контроля над такими проектами они изменяли файлы PKGBUILD и .install, добавляя команду npm install atomic-lockfile. Под видом обычной npm-зависимости загружался вредоносный пакет atomic-lockfile версии 1.4.2.
Privilege Escalation
1 technique
Privilege Escalation
Beyond data theft, the malware employed rootkit-style persistence techniques, disguising its active processes as legitimate kernel threads to evade detection by standard process monitors like ps and htop.
Stealth
7 techniques
Stealth
Beyond data theft, the malware employed rootkit-style persistence techniques, disguising its active processes as legitimate kernel threads to evade detection by standard process monitors like ps and htop.
The outer package is a largely functional TypeScript npm package (legitimate atomic-lockfile project) with the ELF binary inserted into its source tree.
Beyond data theft, the malware employed rootkit-style persistence techniques, disguising its active processes as legitimate kernel threads to evade detection by standard process monitors like ps and htop.
A user runs their AUR helper ( yay , paru , or raw makepkg ) to install or update a package.
This means a developer workstation, maintainer machine, or CI/build host could execute the malware as a side effect of building or installing the compromised AUR package.
the attack began Thursday when attackers abused AUR’s stewardship process for adopting orphaned packages to claim ownership of abandoned, legitimate packages and modify them with malicious PKGBUILD post-install scripts.
После получения контроля над такими проектами они изменяли файлы PKGBUILD и .install, добавляя команду npm install atomic-lockfile. Под видом обычной npm-зависимости загружался вредоносный пакет atomic-lockfile версии 1.4.2.
Credential Access
4 techniques
Credential Access
Once installed, the malicious npm packages deployed a multi-stage infostealer payload engineered to exfiltrate a broad range of sensitive data, including: Browser credentials — saved passwords, session cookies, and autofill data from Chromium and Firefox-based browsers.
SSH private keys — enabling attackers to pivot to remote servers and infrastructure System environment variables — potentially exposing API tokens, cloud credentials, and application secrets Cryptocurrency wallet data — targeting local wallet files and seed phrases.
Once installed, the malicious npm packages deployed a multi-stage infostealer payload engineered to exfiltrate a broad range of sensitive data, including: Browser credentials — saved passwords, session cookies, and autofill data from Chromium and Firefox-based browsers.
SSH private keys — enabling attackers to pivot to remote servers and infrastructure
Command and Control
1 technique
Command and Control
The malicious dependencies act as loaders to retrieve a Rust-based infostealer targeting developer credentials and secrets
Recent activity
3 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.