NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
Malicious package

@nf-addons/am-global-headernpm

Advisory published Updated

@nf-addons/am-global-header is a confirmed malicious npm package (MAL-2026-17154) that steals credentials and exfiltrates sensitive data (malicious version 9.9.10). Do not install it — remove it immediately and rotate any exposed credentials.

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

MAL-2026-17154
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall @nf-addons/am-global-header

What this malware does

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.

Malicious versions

1 flagged
9.9.10

Indicators of compromise (SHA-256)

5f4f7297a2ae76eee65506183462a7138df6115ee2bfad9c84878b7f3c7998c8

Detection & response playbook

Credential / info stealer

  1. Find it

    Search your lockfiles and build artifacts for @nf-addons/am-global-header (version 9.9.10).

  2. If you installed it — respond

    @nf-addons/am-global-header 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.

  3. Did it already run?

    If @nf-addons/am-global-header was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. @nf-addons/am-global-header on npm has been identified as a malicious package (version 9.9.10 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-020504

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks @nf-addons/am-global-header-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
@nf-addons/am-global-header (npm) malicious package — MAL-2026-17154 | O3 Security