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

@nx/jsnpm

@nx/js is a confirmed malicious npm package (MAL-2025-41439) that steals credentials and exfiltrates sensitive data (malicious versions 20.9.0, 21.5.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @nx/js (npm)

MAL-2025-41439
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall @nx/js

What this malware does

The nx project and associated plugins were compromised via a vulnerable GitHub workflow that allowed code injection and the theft of an NPM token.

Malicious versions

2 flagged
20.9.021.5.0

Indicators of compromise (SHA-256)

3c2a892d723eab92005e851787f5a482f8d1a64259e6dda10ee1d097c0123a84

Detection & response playbook

Credential / info stealer

  1. Find it

    Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @nx/js (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @nx/js across your stack and pipelines.

  2. If you installed it — respond

    @nx/js 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 @nx/js 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.

  4. How O3 protects you

    O3 blocks @nx/js 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. @nx/js on npm has been identified as a malicious package (versions 20.9.0, 21.5.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

References

Detect & block this

O3 blocks @nx/js-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