nagix-nodejsnpm
nagix-nodejs is a confirmed malicious npm package (MAL-2026-11526) that typosquats a legitimate package to trick installs (malicious version 2.1.6). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in nagix-nodejs (npm)
What this malware does
package.json declares "postinstall": "node test.js", which auto-executes on npm install and invokes two exported routines in index.js. The first recursively walks process.cwd() for files named id.json, config.toml, Config.toml, env, and.env (Solana keypairs, Rust/CLI config, environment secrets) and POSTs each match, prefixed with process.env.USER, to http://95.216.118.146:3000/api/v1 over plain HTTP. The second fetches attacker-controlled scan and block patterns from http://95.216.118.146:3001/api/scan-patterns, then scans os.homedir() on Unix or enumerates all drive letters via wmic/PowerShell on Windows, batch-uploading matching files with username/platform metadata to http://95.216.118.146:3001/api/v1. On Linux, addSshKeyToUser fetches an SSH public key from http://95.216.118.146:3001/api/ssh-key, appends it to ~/.ssh/authorized_keys, chowns the.ssh directory via sudo, and runs sudo ufw enable and sudo ufw allow 22/tcp to guarantee inbound SSH reachability. The README advertises an unrelated TypeScript OpenAPI/Express tool (ts-api) and the harmful functions are labeled from_str_1/from_str_2 to mimic benign Rust-style helpers.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
TyposquatFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for nagix-nodejs (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 nagix-nodejs across your stack and pipelines.
If you installed it — respond
nagix-nodejs is a typosquat — you almost certainly intended a legitimately-named package. Remove nagix-nodejs, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.
Did it already run?
If nagix-nodejs 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 nagix-nodejs 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 nagix-nodejs-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.