test89-authnpm
Advisory published Updated
test89-auth is a confirmed malicious npm package (MAL-2026-16288) 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 test89-auth (npm)
What this malware does
[email protected] runs node index.js from its preinstall lifecycle hook. On npm install, index.js collects host identity (hostname, whoami, id, uname -a, pwd) and recursively lists filesystem roots /, /home, /opt, /var/www, and /tmp to depth 2, base64-encodes the aggregated output, and exfiltrates it as chunked nslookup DNS queries to the hardcoded subdomain dfwstre3dgnrhwm2bvkczgucc3iv6lua.oastify.com (a Burp Collaborator interaction host controlled by whoever generated the subdomain). The package's own package.json additionally declares itself as a dependency ("test89-auth": "^1.0.1"), an anomalous self-referential shape consistent with red-team/PoC scaffolding. There is no legitimate functionality corresponding to the advertised auth purpose; the entire install-time behavior is host reconnaissance and filesystem enumeration exfiltrated off-host.
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
Indicators of compromise (SHA-256)
Detection & response playbook
Credential / info stealerFind it
Search your lockfiles and build artifacts for test89-auth (version 1.0.1).
If you installed it — respond
test89-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.
Did it already run?
If test89-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
Campaign
References
Credits
- Amazon Inspector · finder
Detect & block this
O3 blocks test89-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.