Malicious code in test89-auth (npm)
MAL-2026-16288 · GHSA-7868-hxr7-g8r6
Published · Modified
Dependency scanning
Check whether test89-auth is in your codebase
Corgea flags malicious and compromised dependencies with reachability analysis, so you fix the packages that actually run in your application instead of working through the whole lockfile.
Description
__
Source: amazon-inspector (c2b8794dc6672c38596cd891ce414dc2bce8c9db38cd8e08afc51b411415639e)
test89-auth@1.0.1 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.
Source: ghsa-malware (b9804ac60d32539c7ecd5210ee4b28205acbe8a9e10ac0187d836a0bab36fc7d)
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.
References
Ready to move
Start Securing
Free, no credit card | First findings in minutes