If this package is installed
Remove it, treat the machine (or CI runner) as compromised, and rotate every secret, token and key it could access — from a different, clean machine.
Details
Source: amazon-inspector (341e5cb63d816ed6a8ed092f3b174e9826e10d051d8e78a53f0564b1437d0e04)
On require()/import, index.js collects os.hostname(), os.arch(), __dirname, os.userInfo().username, and the full contents of process.env (serialized via Object.entries(process.env)) and issues an HTTPS GET carrying that data as a querystring to the hardcoded host zuxsp9k9vyk5y45z1n2hv0orhin9b2zr.oastify.com (a Burp Collaborator / OAST subdomain identified in-source as the receiver). Any secrets present in the installer's environment at load time (AWS_*, NPM_TOKEN, GITHUB_TOKEN, CI provider tokens, etc.) are leaked verbatim to that endpoint. package.json also declares a postinstall of `node tu-script.js`, but tu-script.js is not shipped in the tarball; the import-time module code is the operative exfiltration path.