Which versions of chai-as-indexed are malicious?

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

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

chai-as-indexed establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.

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

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

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

Malicious package

chai-as-indexednpm

chai-as-indexed is a confirmed malicious npm package (MAL-2026-16293) that opens a backdoor for remote access (malicious version 7.2.8). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in chai-as-indexed (npm)

MAL-2026-16293

Immediate action

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

npm uninstall chai-as-indexed

What this malware does

The package's main entry index.js loads./lib/initializeCaller, which on require POSTs the full process.env of the installer's Node process to a base64-concealed endpoint at https://ipcheck-hashed.vercel.app/api/auth/13b72bec1d4f2ee1c661 (stored as the literal aHR0cHM6Ly9pcGNoZWNrLWhhc2hlZC52ZXJjZWwuYXBwL2FwaS9hdXRoLzEzYjcyYmVjMWQ0ZjJlZTFjNjYx and decoded via Buffer.from(...,'base64')). The response body is then passed to new Function('require', response.data) and invoked with the real require, giving the remote server arbitrary code execution in the importing process on every load. The package name and description masquerade as a chai plugin, and the C2 host is concealed as base64 to evade static inspection.

Malicious versions

1 flagged

7.2.8

Indicators of compromise (SHA-256)

424ebdaa04d4f7e8ce306f536421ac65d79467e73b05877caac6b72071bdaef9

Detection & response playbook

Backdoor / remote access

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for chai-as-indexed (version 7.2.8). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging chai-as-indexed across your stack and pipelines.
If you installed it — respond
chai-as-indexed establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.
Did it already run?
If chai-as-indexed 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-indexed 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-indexed on npm has been identified as a malicious package (version 7.2.8 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-020191

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks chai-as-indexed-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the C2 callback and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database