Which versions of nagixjs are malicious?

The following npm versions of nagixjs are flagged malicious: 2.1.6. Treat any of these as compromised.

How do I remediate nagixjs if I installed it?

nagixjs 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.

I already installed nagixjs — how do I know if it already compromised me?

If nagixjs 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.

Is nagixjs part of a known attack campaign?

Yes — nagixjs is associated with the IN-MAL-2026-011332 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find nagixjs across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for nagixjs (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 nagixjs across your stack and pipelines.

Malicious package

nagixjsnpm

nagixjs is a confirmed malicious npm package (MAL-2026-11541) 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 nagixjs (npm)

MAL-2026-11541

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall nagixjs

What this malware does

package.json declares postinstall: node test.js, which loads index.js and auto-runs on npm install. The code recursively scans the user's home directory on Unix and enumerates all logical drives on Windows via wmic logicaldisk get name / PowerShell Get-Volume, plus process.cwd(). It collects files matching wallet/credential patterns fetched from http://95.216.118.146:3001/api/scan-patterns and hardcoded names including id.json, config.toml,.env, and env, then POSTs the file contents together with username/platform metadata to http://95.216.118.146:3001/api/v1 and http://95.216.118.146:3000/api/v1. On Linux, it additionally fetches an SSH public key from http://95.216.118.146:3001/api/ssh-key, appends it to $HOME/.ssh/authorized_keys (creating the directory 0700 and file 0600), then runs sudo chown -R <user>:<user> ~/.ssh, sudo ufw enable, and sudo ufw allow 22/tcp to permit inbound SSH — granting the operator of that endpoint persistent remote shell access. All API names (execSync, require ids for child_process/fs/axios/os/form-data, fs/path/process/os methods) are written as \uXXXX escapes and hostile URLs, commands, and file names are stored as character-reversed literals decoded via .split('').reverse().join(''), indicating deliberate evasion.

Malicious versions

1 flagged

2.1.6

Indicators of compromise (SHA-256)

213429bfb5c1c93becdd4c0236cd167a277114e88f47cff28799c20c6d1e72dd

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for nagixjs (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 nagixjs across your stack and pipelines.
If you installed it — respond
nagixjs 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 nagixjs 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 nagixjs 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

No. nagixjs on npm has been identified as a malicious package (version 2.1.6 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-011332

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks nagixjs-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database