Which versions of chlklib are malicious?

The following npm versions of chlklib are flagged malicious: 1.2.0, 1.2.1, 1.2.2, 1.2.3. Treat any of these as compromised.

How do I remediate chlklib if I installed it?

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.

I already installed chlklib — how do I know if it already compromised me?

If chlklib 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.

Is chlklib part of a known attack campaign?

Yes — chlklib is associated with the IN-MAL-2026-007526, IN-MAL-2026-007527, IN-MAL-2026-007529, IN-MAL-2026-007528 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find chlklib across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for chlklib (4 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging chlklib across your stack and pipelines.

Malicious package

chlklibnpm

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)

MAL-2026-6470

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall chlklib

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.

Malicious versions

4 flagged

1.2.01.2.11.2.21.2.3

Indicators of compromise (SHA-256)

136a65e3a9bd3712d0e949a0a9b56747918d7d1436cbad01e204ab23ff5e990f

766413ce8bb9e5a330bf1a6f878e75a03528339df61dac409a66a06218e082d4

b08a933891c92fdec26fbadf4921d2e08ff101126fb656a2b57d747fefa9d0d4

fe013bde99ee7eafc14dc4db6ac67e239dd3ee3be046c2444c69b07181b236a3

Detection & response playbook

Typosquat

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for chlklib (4 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging chlklib across your stack and pipelines.
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 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 chlklib 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

No. chlklib on npm has been identified as a malicious package (versions 1.2.0, 1.2.1, 1.2.2, 1.2.3 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-007526IN-MAL-2026-007527IN-MAL-2026-007529IN-MAL-2026-007528

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.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database