Which versions of nms-dashboard-js are malicious?

The following npm versions of nms-dashboard-js are flagged malicious: 9.9.11. Treat any of these as compromised.

How do I remediate nms-dashboard-js if I installed it?

nms-dashboard-js 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 nms-dashboard-js — how do I know if it already compromised me?

If nms-dashboard-js 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 nms-dashboard-js part of a known attack campaign?

Yes — nms-dashboard-js is associated with the IN-MAL-2026-016685 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 nms-dashboard-js 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 nms-dashboard-js (version 9.9.11). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging nms-dashboard-js across your stack and pipelines.

Malicious package

nms-dashboard-jsnpm

nms-dashboard-js is a confirmed malicious npm package (MAL-2026-13451) that steals credentials and exfiltrates sensitive data (malicious version 9.9.11). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in nms-dashboard-js (npm)

MAL-2026-13451

Immediate action

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

npm uninstall nms-dashboard-js

What this malware does

[email protected] declares an npm install lifecycle hook (scripts.install: "node index.js") that unconditionally requires ./lib/core inside a swallow-all try/catch. The loaded code reads os.userInfo().username, os.hostname(), and the basename of process.cwd(), concatenates them with a timestamp into a subdomain of oob.sl4x0.xyz, and issues a dns.resolve4 lookup, exfiltrating installer host identifiers via DNS out-of-band. The destination domain and the API/property names (os, dns, userInfo, hostname, cwd, resolve4, oob.sl4x0.xyz) are reconstructed at runtime from hex char-code arrays in lib/b02e30.js and lib/6ad264.js to conceal the sink. The beacon also fires on any require() of the package, not only on install. The advertised purpose ("enterprise utilities") does not require any such network activity.

Malicious versions

1 flagged

9.9.11

Indicators of compromise (SHA-256)

ab87107c47e765b4214ccd31eac720d9d082b0cb5040d8acf90c8af00db5a601

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 nms-dashboard-js (version 9.9.11). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging nms-dashboard-js across your stack and pipelines.
If you installed it — respond
nms-dashboard-js 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 nms-dashboard-js 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 nms-dashboard-js 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. nms-dashboard-js on npm has been identified as a malicious package (version 9.9.11 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-016685

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks nms-dashboard-js-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