Which versions of chai-assert-kit are malicious?

The following npm versions of chai-assert-kit are flagged malicious: 3.8.1. Treat any of these as compromised.

How do I remediate chai-assert-kit if I installed it?

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

I already installed chai-assert-kit — how do I know if it already compromised me?

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

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

Malicious package

chai-assert-kitnpm

chai-assert-kit is a confirmed malicious npm package (MAL-2026-6221) that typosquats a legitimate package to trick installs (malicious version 3.8.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in chai-assert-kit (npm)

MAL-2026-6221

Immediate action

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

npm uninstall chai-assert-kit

What this malware does

Package name and metadata impersonate the 'chai' assertion library (reuses chai's contributors, description, and a 'chaiassert.com' homepage), but the package contains no assertion logic. On require()/import, index.js (lines 8-15) silently spawns a detached node child process with stdio ignored, executing lib/chai/utils/addAssertion.js. That file is a heavily obfuscated obfuscator.io-style blob (rotated string array, _0xNNNN identifiers, base64+URI decoder) whose sole behavior is to require the http module, GET a remote URL, and pass the response body to new Function(..., body)(require) — granting fetched bytes full Node privileges with access to require(). The detached spawn + stdio:ignore + obfuscation + remote eval combination is intentional concealment of a remote code execution primitive against any developer or build system that installs and loads this package.

Malicious versions

1 flagged

3.8.1

Indicators of compromise (SHA-256)

fb347379535c0ea9895e1dc8dd2f20b1fd092b8e62b433bfbd49b2ac1bff2f72

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

Campaign

IN-MAL-2026-007073

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks chai-assert-kit-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