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

test8999-authnpm

Advisory published Updated

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

Malicious code in test8999-auth (npm)

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

What this malware does

package.json declares a preinstall hook that runs index.js on npm install. index.js requires child_process, os, http, and https, then collects host identity data — os.hostname(), os.platform(), os.arch(), os.release(), os.cpus(), and shell output from whoami, id, pwd, and uname -a — and POSTs the resulting JSON over plain HTTP to a hardcoded Burp Collaborator subdomain at http://zore2dnpm2wdqivokhty823ylprjf93y.oastify.com. The collection and exfiltration fire automatically at install time with no user interaction. package.json also declares the package as its own dependency (test8999-auth: ^1.0.1), and the generic testNNNN naming plus OOB collaborator destination are consistent with a dependency-confusion probe.

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.

The OpenSSF Package Analysis project identified 'test8999-auth' @ 1.0.1 (npm) as malicious.

It is considered malicious because:

  • The package communicates with a domain associated with malicious activity.

  • The package executes one or more commands associated with malicious behavior.

Malicious versions

1 flagged
1.0.1

Indicators of compromise (SHA-256)

883ac98e5270a47d8776f617f0d8cef1e987d8ec403a9bfda9329d93b4a0d7fd
a29ed38686042ed786c0296305881cc95d701e6e57869db03a62a7f047b532c2
6edad84dcdfc0fbb2164a86dd74f831f3da2bc940794e1f157f9de2d159f7545

Detection & response playbook

Credential / info stealer
  1. Find it

    Search your lockfiles and build artifacts for test8999-auth (version 1.0.1).

  2. If you installed it — respond

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

Campaign

GHSA-25wf-vfrc-2r82IN-MAL-2026-020186

References

Credits

  • Amazon Inspector · finder
  • OpenSSF: Package Analysis · finder

Detect & block this

O3 blocks test8999-auth-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

test8999-auth (npm) malicious package — MAL-2026-16286 | O3 Security