Which versions of chai-as-polished are malicious?

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

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

chai-as-polished is a typosquat — you almost certainly intended a legitimately-named package. Remove chai-as-polished, 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-polished — how do I know if it already compromised me?

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

Yes — chai-as-polished is associated with the IN-MAL-2026-006794, GHSA-jpr9-h23w-g7gg, RLMA-2026-05508 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-polished 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-polished (version 7.0.8). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging chai-as-polished across your stack and pipelines.

Malicious package

chai-as-polishednpm

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

Malicious code in chai-as-polished (npm)

MAL-2026-5901

Immediate action

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

npm uninstall chai-as-polished

What this malware does

Package name is a one-edit typosquat of the widely-used chai-as-promised, but the shipped code is unrelated to chai. The exported middleware spawns a detached, unref'd child process running lib/initializeCaller.js. That file constructs a fake process.env containing three base64-encoded fields which decode to the URL https://tomato-brunhilda-40.tiiny.site/index.json and the header x-secret-key: _, fetches that URL via axios, and passes response.data.cookie to new Function.constructor('require', response)(require) — executing arbitrary attacker-supplied JavaScript with the installer's Node require available. The base64 staging of the URL and header has no functional purpose other than to hide the destination from cursory review. tiiny.site is an anonymous static-hosting service whose contents the author can change at any time, so the executed payload is fully attacker-controlled and mutable. Triggering requires a consumer to invoke the package's middleware, which is the documented entry point for anyone deceived by the name into installing it.

Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

Malicious versions

1 flagged

7.0.8

Indicators of compromise (SHA-256)

b2ea0d46e0bb4382e8d684d025cb72b7f99e37874c571e9946ae1268b70be6cf

869d873d0e1d2cf40fe6383629d3c195a5d8aca6d93a67cc04c5f54eab38bf57

5b318655cb5ab4f84b593aaebba844fa4d5e2ee195d9de230aa0dac0ceea42e9

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

Campaign

IN-MAL-2026-006794GHSA-jpr9-h23w-g7ggRLMA-2026-05508

References

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

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