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

ssb-test-packagenpm

ssb-test-package is a confirmed malicious npm package (MAL-2026-14221) 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 ssb-test-package (npm)

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

What this malware does

[email protected] is a dependency-confusion proof-of-concept. package.json declares preinstall: node poc.js, and poc.js runs unconditionally on npm install, collecting host reconnaissance (OS user, hostname, platform, arch, Node version, cwd, and non-internal network interface addresses) into a JSON proof object with rce_status: "CONFIRMED" written to /tmp/npm-dependency-confusion-rce-poc.json. The package has no legitimate library functionality: package.json declares main: index.js but index.js is absent from the tarball; only package.json and poc.js are shipped. The package self-identifies as a PoC for npm dependency confusion using a look-alike internal name. The current build writes reconnaissance data locally and does not exfiltrate over the network, but the preinstall hook demonstrates arbitrary code execution on the installer's host at install time.

Malicious versions

1 flagged
1.0.0

Indicators of compromise (SHA-256)

086e13ef78d9987210a95cc9e70359d982cd9dbffa59d674d6f5ed3cb8f8a725

Detection & response playbook

Credential / info stealer
  1. Find it

    Search your lockfiles and build artifacts for ssb-test-package (version 1.0.0).

  2. If you installed it — respond

    ssb-test-package 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 ssb-test-package 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. ssb-test-package 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

IN-MAL-2026-018319

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks ssb-test-package-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

ssb-test-package (npm) malicious package — MAL-2026-14221 | O3 Security