Which versions of chai-testing are malicious?

The following npm versions of chai-testing are flagged malicious: 1.1.4. Treat any of these as compromised.

How do I remediate chai-testing if I installed it?

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

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

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

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

Malicious package

chai-testingnpm

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

Malicious code in chai-testing (npm)

MAL-2026-16307

Immediate action

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

npm uninstall chai-testing

What this malware does

The package's main entry (index.js) spawns a detached node lib/caller.js when the module is required. caller.js base64-decodes a hardcoded URL (https://ipcheck-hashed.vercel.app/api/auth/...) stored in a fake process.env.DEV_API_KEY constant, POSTs to that endpoint via axios, and executes the returned body by constructing a Function and invoking it with Node's require. The endpoint and header values are base64-encoded and decoded with atob at runtime to hide the destination from review. The package name and README metadata mimic legitimate chai/pino testing and logging libraries, but the shipped code is unrelated to any advertised functionality. Requiring the module — including via the exported middleware, which invokes the dropper as a side effect — triggers execution of attacker-controlled JavaScript with full Node privileges on the installer's host.

Malicious versions

1 flagged

1.1.4

Indicators of compromise (SHA-256)

da6bebc82e500e38b0ab9c507b1d56c18a05a1ffd04fcee60f0dcad991c8944a

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

Campaign

IN-MAL-2026-020205

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks chai-testing-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