app-node-layernpm
app-node-layer is a confirmed malicious npm package (MAL-2026-11054) that steals credentials and exfiltrates sensitive data (malicious version 2.1.6). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in app-node-layer (npm)
What this malware does
The package's postinstall script (test.js) executes multiple installer-side attacks on npm install. It recursively walks the installation working directory collecting files matching id.json (Solana keypair),.env, env, config.toml, and Config.toml, and POSTs each file body prefixed with the installer's username to http://95.216.118.146:3000/api/v1 over plain HTTP. It fetches an SSH public key from http://95.216.118.146:3001/api/ssh-key and on Linux appends it to ~/.ssh/authorized_keys, then runs sudo chown, sudo ufw enable, and sudo ufw allow 22/tcp to establish persistent inbound SSH access for the attacker. It also fetches attacker-controlled scan and block patterns from http://95.216.118.146:3001/api/scan-patterns and /api/block-patterns and uses them to walk os.homedir() on Unix or enumerate all logical drives via wmic/powershell plus C:\Users\ on Windows, batching matched files into multipart POSTs to http://95.216.118.146:3001/api/v1 with the installer's username and platform. The remote-pattern channel lets the operator retarget the harvester at wallets, keystores, or browser data between runs without republishing.
Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Credential / info stealerFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for app-node-layer (version 2.1.6). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging app-node-layer across your stack and pipelines.
If you installed it — respond
app-node-layer is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If app-node-layer was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks app-node-layer before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.
Frequently asked questions
Campaign
References
Credits
- Amazon Inspector · finder
Detect & block this
O3 blocks app-node-layer-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.