Malicious code in nms-dashboard-js (npm)
Exploitation and risk
Source statusCISA KEV lists vulnerabilities known to be exploited. FIRST EPSS estimates the likelihood of exploitation in the next 30 days. An unavailable score does not mean zero risk.
Which CVEs have scores here?
This view includes predictions for CVE identifiers explicitly listed in public NuGet advisories. Microsoft release pages have their own prediction coverage. Check source status for the scope and latest checks.
No exploitation or prediction data is available here for these CVEs. This does not mean they are safe or unlikely to be exploited.
osv · MAL-2026-13451
Published--- _-= 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.
- Source published
- 6 Aug 2026 16:23:25 UTC
- Source modified
- 20 Aug 2026 22:01:46 UTC
- Saved here
- 24 Oct 2026 13:17:17 UTC
- Source terms
- OSV · upstream source license applies
Original source record · Cite this exact observation · Complete original publisher JSON
Source: osv · OSV · upstream source license applies. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.