Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Malicious package

blastradarnpm

Advisory published Updated

blastradar is a confirmed malicious npm package (MAL-2026-14120) that steals credentials and exfiltrates sensitive data (malicious version 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in blastradar (npm)

MAL-2026-14120
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall blastradar

What this malware does

The package's index.js loads child_process, https, and fs at the top level and performs an HTTPS POST that carries host- and installer-identifying data (references to process.env, process.cwd(), a hardcoded hostname, and filesystem probes via fs.existsSync). The composition — env/cwd/child_process reads combined with an outbound https.request POST to a hardcoded destination in the main module — matches the shape of an installer-side data exfiltration beacon rather than any documented library function. The package advertises no purpose that would justify posting environment variables and working-directory information to a remote host on load.

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.

Malicious versions

1 flagged
1.0.0

Indicators of compromise (SHA-256)

75d95c6cb483df4961cb4a29d4cde8e4c849ba82678a2fbad90585d4afaa1f1a
e3eccd07c931ee578e1201f5fbb7f4610fd5291202c0fcee2b30c959c80c871e

Detection & response playbook

Credential / info stealer
  1. Find it

    Search your lockfiles and build artifacts for blastradar (version 1.0.0).

  2. If you installed it — respond

    blastradar 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 blastradar 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. blastradar on npm has been identified as a malicious package (version 1.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-pp9x-4g56-7322IN-MAL-2026-017990

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks blastradar-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Explore

blastradar (npm) malicious package — MAL-2026-14120 | O3 Security