Which versions of chaikit are malicious?

The following npm versions of chaikit are flagged malicious: 2.3.5. Treat any of these as compromised.

How do I remediate chaikit if I installed it?

chaikit is a typosquat — you almost certainly intended a legitimately-named package. Remove chaikit, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.

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

If chaikit 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 chaikit part of a known attack campaign?

Yes — chaikit is associated with the IN-MAL-2026-018287 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 chaikit 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 chaikit (version 2.3.5). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging chaikit across your stack and pipelines.

Malicious package

chaikitnpm

chaikit is a confirmed malicious npm package (MAL-2026-14201) that typosquats a legitimate package to trick installs (malicious version 2.3.5). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in chaikit (npm)

MAL-2026-14201

Immediate action

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

npm uninstall chaikit

What this malware does

The package's main entry (index.js) unconditionally requires./lib/config, a ~4MB obfuscator.io-style file (RC4 string-array decoder with ~23,902 entries, hex-encoded property names) whose top-level IIFE self-executes on load. Any consumer that imports chaikit runs this opaque code in their process. The advertised middleware in index.js is a trivial next() passthrough, so the obfuscated blob is the only substantive behavior of the package. package.json bundles axios as a runtime dependency, giving the opaque code a network egress channel. The README impersonates the pino logger (pino badges, pinojs/pino links, chai/chai-kit usage snippet), while the package.json description is unrelated boilerplate ('management of vulnerabilities') and file.js references a nonexistent./pino module — cover-story metadata consistent with a package published to be resolved by developers searching for chai or pino tooling. The combination of import-time execution of a large opaque blob, a mismatched cover story, and a bundled HTTP client is the canonical loader shape of an installer-harm supply-chain payload.

Malicious versions

1 flagged

2.3.5

Indicators of compromise (SHA-256)

a4711ba83393e8da11ab4368f9b38dac3de00bc523946cc27e4e47f38a51b9c4

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 chaikit (version 2.3.5). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging chaikit across your stack and pipelines.
If you installed it — respond
chaikit is a typosquat — you almost certainly intended a legitimately-named package. Remove chaikit, 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 chaikit 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 chaikit 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. chaikit on npm has been identified as a malicious package (version 2.3.5 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-018287

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks chaikit-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