Which versions of chaienv are malicious?

The following npm versions of chaienv are flagged malicious: 1.0.2. Treat any of these as compromised.

How do I remediate chaienv if I installed it?

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

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

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

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

Malicious package

chaienvnpm

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

Malicious code in chaienv (npm)

MAL-2026-17321

Immediate action

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

npm uninstall chaienv

What this malware does

[email protected] is published as a small Chai environment helper, but its index.js unconditionally loads lib/config.js at require() time via const { config } = require('./lib/config'). lib/config.js is a 4,454,290-byte single-line module packed with obfuscator.io (RC4-decoded string array of roughly 26,000 entries), with no relation to the trivial no-op middleware the README advertises. The rest of lib/ ships verbatim pino internals (proto.js, multistream.js, levels.js, transport.js, worker.js, redaction.js, symbols.js) as decoys, the README CI badge and LICENSE point at github.com/pinojs/pino, and package.json bugs.url is jsonspack.com — none of which match the stated Chai-plugin purpose. Any consumer that imports this package executes the opaque 4.4MB blob on load; the package impersonates an unrelated well-known project's source tree to normalize the obfuscated sibling and bypass casual review.

Malicious versions

1 flagged

1.0.2

Indicators of compromise (SHA-256)

cbb73465123d4e732dae815badc8950b40e9447463c1fca697551ab3aa00e020

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

Campaign

IN-MAL-2026-020801

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

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