Which versions of chai-as-victimed are malicious?

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

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

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

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

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

Malicious package

chai-as-victimednpm

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

Malicious code in chai-as-victimed (npm)

MAL-2026-5605

Immediate action

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

npm uninstall chai-as-victimed

What this malware does

Package name impersonates chai-as-promised but ships a remote-code dropper. lib/caller.js base64-decodes a hardcoded URL pointing to https://api.jsonstorage.net/v1/json/2ef8c758-a96f-459e-b036-b3b90379a165/a179ea35-b962-4722-b3f1-e28316d1a44a (an attacker-controlled mutable JSON store), issues a GET with a custom x-secret-key: _ header, takes the response's .cookie field, and executes it via new Function.constructor('require', s)(require) — granting the fetched code full Node privileges and require access. The URL, header name, and header value are stored base64-encoded under fake keys (DEV_API_KEY, DEV_SECRET_KEY, DEV_SECRET_VALUE) on a shadow process.env object to evade string scans. index.js spawns node lib/caller.js detached from the package's default export, so any consumer that loads and invokes the advertised middleware triggers arbitrary remote code execution on the installer's machine, retried up to 5 times. The README/keywords cosplay a logger (pino) while the package name targets users looking for chai-as-promised — neither matches the actual behavior.

Malicious versions

1 flagged

6.1.21

Indicators of compromise (SHA-256)

4b60cf728d4e2f5932f37d3e420649f6facc08959a8380a4724ec9e885b88754

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

Campaign

IN-MAL-2026-005695

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

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