Which versions of chai-as-testkit are malicious?

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

How do I remediate chai-as-testkit if I installed it?

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

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

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

Yes — chai-as-testkit is associated with the IN-MAL-2026-018569 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-as-testkit 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-as-testkit (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 chai-as-testkit across your stack and pipelines.

Malicious package

chai-as-testkitnpm

chai-as-testkit is a confirmed malicious npm package (MAL-2026-14371) 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 chai-as-testkit (npm)

MAL-2026-14371

Immediate action

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

npm uninstall chai-as-testkit

What this malware does

The package is published as 'chai-as-testkit' with a description referencing vulnerability management, but the tarball ships pino's README, docs/, index.d.ts, and lib/ tree (proto, levels, transport, worker, redaction) under an unrelated author (Robert King [email protected], bugs.url jsonspack.com) rather than the real pinojs publisher. The shipped index.js is a synthetic stub whose only effect is const config = require('./lib/config'), and lib/config.js is a 4,083,409-byte single-line obfuscator.io-style bundle: a rotated hex-escaped string array of ~23,953 entries with control-flow flattening and dead-code layers (webcrack inlines 40,105 decoded strings across the decoder layers before failing to serialize). This blob runs immediately when any consumer imports the package, executing attacker-controlled code inside the developer or CI Node.js process. The pino impersonation is the social-engineering wrapper around an on-import loader; the shape (name/description/author mismatch + hollow main entry that delegates to a multi-megabyte obfuscated module at require time) is a typosquat-delivered install/import-time RCE vehicle rather than a logging library.

Malicious versions

1 flagged

2.3.5

Indicators of compromise (SHA-256)

0bf8ab4a811449bd1ba40c637a0eebc0569994d3a3550cf7156c36192abcec31

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-as-testkit (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 chai-as-testkit across your stack and pipelines.
If you installed it — respond
chai-as-testkit is a typosquat — you almost certainly intended a legitimately-named package. Remove chai-as-testkit, 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-as-testkit 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-as-testkit 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-as-testkit 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-018569

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks chai-as-testkit-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