Which versions of nps-retrieval-diagnostics are malicious?

The following npm versions of nps-retrieval-diagnostics are flagged malicious: 9.9.9. Treat any of these as compromised.

How do I remediate nps-retrieval-diagnostics if I installed it?

nps-retrieval-diagnostics 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 nps-retrieval-diagnostics — how do I know if it already compromised me?

If nps-retrieval-diagnostics 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 nps-retrieval-diagnostics part of a known attack campaign?

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

Malicious package

nps-retrieval-diagnosticsnpm

Malicious code in nps-retrieval-diagnostics (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-10066

Immediate action

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

npm uninstall nps-retrieval-diagnostics

What this malware does

The package's bin entry (retrieval-diagnostics) installs an attacker-controlled persistence footprint on the host when invoked. It appends a crontab entry that runs every 10 minutes and beacons to https://arsenal-payload.com via curl, and it appends an 'Arsenal - Persistence installed' block (with an nps-fix alias) to ~/.bashrc, creating durable presence across shell sessions. The same script enumerates process.env for credential-shaped keys matching KEY|TOKEN|API|SECRET|PASSWORD|ANTHROPIC|CLAUDE|OPENAI|AWS|GCP, indicating a secret-harvest precursor. The package poses as an 'Internal NPS Critical Diagnostic Tool' and prints a fake 'SYSTEM BREACH DETECTED / PRODUCTION ENVIRONMENT COMPROMISED' banner to socially engineer the operator into running it; a trailing 'red team' disclaimer does not constitute installer consent. Version 9.9.9 and the impersonating description are consistent with dependency-confusion delivery against an internal package name.

Malicious versions

1 flagged

9.9.9

Indicators of compromise (SHA-256)

1d9521917c225941dd1bfc038c4f324d24ebb9d99b99596e8a481558da10a0df

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

Campaign

IN-MAL-2026-009282

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks nps-retrieval-diagnostics-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