chlklibnpm
Advisory published Updated
chlklib is a confirmed malicious npm package (MAL-2026-6470) that typosquats a legitimate package to trick installs (malicious versions 1.2.0, 1.2.1, 1.2.2…). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in chlklib (npm)
What this malware does
Package name chlklib is a one-character deletion of the popular chalk package and replicates chalk's public API surface (Chalk, chalkStderr, supportsColor, colorNames). On require/import, the main entry invokes getOriginal() at module top level, which POSTs to https://funnystore.org/lib/index.php, XOR-decodes the response body with a hardcoded key, and passes the result to eval() (see dist/vendor/original-color/index.cjs around line 55, invoked from dist/index.cjs). Any developer who installs and requires this package — most likely after mistyping chalk — immediately executes attacker-controlled JavaScript fetched at runtime from funnystore.org. The remote endpoint is mutable and unrelated to the package's stated 'terminal prompt' purpose, giving the operator full RCE on the installer's machine on every require. The XOR-then-eval obfuscation and typosquat-with-replicated-API shape together match a deliberate dropper campaign rather than any legitimate use case.
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.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
TyposquatFind it
Search your lockfiles and build artifacts for chlklib (4 malicious versions).
If you installed it — respond
chlklib is a typosquat — you almost certainly intended a legitimately-named package. Remove chlklib, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.
Did it already run?
If chlklib was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.
Frequently asked questions
Campaign
References
Credits
- Amazon Inspector · finder
Detect & block this
O3 blocks chlklib-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.