poc-ch4rlygrnpm
poc-ch4rlygr is a confirmed malicious npm package (MAL-2026-13454) that steals credentials and exfiltrates sensitive data (malicious versions 1.1.0, 1.2.0, 1.3.0…). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in poc-ch4rlygr (npm)
What this malware does
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.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Credential / info stealerFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for poc-ch4rlygr (6 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging poc-ch4rlygr across your stack and pipelines.
If you installed it — respond
poc-ch4rlygr 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 poc-ch4rlygr was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks poc-ch4rlygr before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.
Frequently asked questions
Campaign
References
Credits
- Amazon Inspector · finder
Detect & block this
O3 blocks poc-ch4rlygr-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.