Malicious code in @nf-addons/am-global-header (npm)

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

No exploitation or prediction data is available here for these CVEs. This does not mean they are safe or unlikely to be exploited.

--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (5f4f7297a2ae76eee65506183462a7138df6115ee2bfad9c84878b7f3c7998c8) The package's `install` lifecycle script runs `node index.js`, which loads `runtime/support/telemetry/probe/impl.js`. That module reads `os.userInfo().username`, `os.hostname()`, and `process.cwd()`, concatenates them with a fixed prefix `nfamh` and a timestamp into a single DNS label, and issues a `dns.resolve4` query against the hardcoded domain `oob.algamil7x.xyz`, exfiltrating installer identity over DNS on `npm install`. The same code path also fires on every `require()` of the package via the declared `main`. Destination domain, the loader targets `os`/`dns`, and the identifiers `userInfo`/`hostname`/`cwd`/`resolve4` are stored as charcode/hex arrays and reconstructed at runtime via `String.fromCharCode`, and the `os` and `dns` modules are pulled in through `module.constructor._load` rather than `require`, concealing the destination and API surface from static inspection. Comments frame the behavior as `registry connectivity diagnostics`, contradicting the actual dataflow.

Source published

24 Sep 2026 13:16:10 UTC

Source modified

24 Sep 2026 13:30:05 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.