OpenSSF/OSV advisory MAL-2026-13454 confirms this npm version as malicious. 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)...
Source
OpenSSF Malicious Packages via OSV
Summary
Malicious code in poc-ch4rlygr (npm)
Details
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.
Decision reason
OpenSSF Malicious Packages via OSV confirms poc-ch4rlygr@1.2.0 as malicious (MAL-2026-13454): Malicious code in poc-ch4rlygr (npm)