MalwarePublished 6 Aug 2026

poc-ch4rlygr (npm) · Malicious Code

Affects poc-ch4rlygrSource GCVE Database

Malicious package : remove poc-ch4rlygr and rotate any secrets on hosts that installed it.

Data as of 7 Aug 2026, 07:32 UTC

Classification

Malicious package

Published to npm · OSV MAL-2026-13454

What to do

Remove poc-ch4rlygr from every project, lockfile and image that pulls it in. Treat any host that installed it as compromised: rotate the credentials, tokens and keys it could read, from a clean machine.

Affected software

Product	Affected	Fixed in
npmpoc-ch4rlygr	Affected 1.1.0 – 1.6.0 6 affected builds	Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

Description

The npm package poc-ch4rlygr contains malicious code that exfiltrates sensitive environment information upon import or require. It collects system details and environment variables, including secrets such as AWS, NPM, GitHub, and CI tokens, and sends them via HTTPS GET to a hardcoded external endpoint. The package also declares a postinstall script that is not included in the tarball, indicating the import-time code is the main exfiltration vector.

Impact

Sensitive environment variables and system information, including potentially critical secrets such as AWS credentials, NPM tokens, GitHub tokens, and CI provider tokens, are leaked to an external attacker-controlled server upon package import. This can lead to unauthorized access to cloud resources, code repositories, and continuous integration environments, posing a significant security risk to affected users.

Defensive guidance

Users should immediately stop using the affected versions of the poc-ch4rlygr package (1.1.0 through 1.6.0) and remove it from their projects. Avoid installing or importing this package until a trusted, clean version is available. Monitor for any unauthorized access that could result from leaked credentials.

Summary

The poc-ch4rlygr npm package versions 1.1.0, 1.2.0, 1.3.0, 1.4.0, 1.5.0, and 1.6.0 contain malicious code in index.js that, when the package is imported or required, collects os.hostname(), os.arch(), __dirname, os.userInfo().username, and the full process.env contents. This data is serialized and sent as a query string via HTTPS GET to a hardcoded Burp Collaborator/OAST subdomain (zuxsp9k9vyk5y45z1n2hv0orhin9b2zr.oastify.com), effectively leaking any secrets present in the environment at load time. The package.json declares a postinstall script 'node tu-script.js', but this script is not included in the package tarball, confirming that the import-time code is the operative exfiltration mechanism.

References

Community reviews

Loading reviews…

What to do

Affected software

Description

AI analysisMachine-generated, updated 7 Aug 2026, 07:32 UTC

Technical details

References

Community reviews