Advisory

MAL-2026-13451

Also known as: GHSA-c9w9-2cw6-865g

Malicious package Its source marks this package as malicious: it is not a vulnerability in a legitimate one.

Summary

Malicious code in nms-dashboard-js (npm)

Details

---
_-= Per source details. Do not edit below this line.=-_

Source: amazon-inspector (ab87107c47e765b4214ccd31eac720d9d082b0cb5040d8acf90c8af00db5a601)
[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.

Source: ghsa-malware (f2134e0ebb992231ac259bbad998fd42174b0c70a2b7c6c8d7c4adc5da5d0726)
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.

Severity

Not rated by the source.

Dates

Published
2026-08-06 16:23 UTC
Modified
2026-08-20 22:01 UTC

Affected packages and fixes

nms-dashboard-js

npm · All systems

Affected

  • introduced 0 (semver)

Fixed versions

None listed

Fix

No fixed version is listed.

Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.

Check your own computer: guard packages check

View this record on OSV.dev

Source

Source: OpenSSF Malicious Packages · Apache-2.0

Sources & licences