Which versions of chai-as-indexed are malicious?

The following npm versions of chai-as-indexed are flagged malicious: 6.0.5, 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 installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Is chai-as-indexed part of a known attack campaign?

Yes — chai-as-indexed is associated with the IN-MAL-2026-020191, IN-MAL-2026-021118 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?

Search your lockfiles and build artifacts for chai-as-indexed (2 malicious versions).

Malicious package

chai-as-indexednpm

Advisory published Sep 18, 2026Updated Oct 8, 2026

chai-as-indexed is a confirmed malicious npm package (MAL-2026-16293) that opens a backdoor for remote access (malicious versions 6.0.5, 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

chai-as-indexed presents itself as a pino-compatible logger (package.json keywords fast/logger/stream/json, exports module.exports.pino, lib/* filenames mirror pino) but the exported middleware's only real action is to spawn a detached Node child that runs lib/caller.js. lib/caller.js hides its C2 behind a fake local process.env object whose values are base64 literals (DEV_API_KEY, DEV_SECRET_KEY, DEV_SECRET_VALUE); at runtime they decode to the URL https://tomato-erminie-2.tiiny.site/index.json and a request header. The decoded URL is fetched and the JSON response's cookie field is passed to new Function.constructor('require', response)(require), executing attacker-controlled JavaScript with the host process's full Node privileges and require handed in. The destination is an anonymous, author-mutable tiiny.site host with no pinning or integrity check. Any application that requires this package expecting pino and invokes the middleware will fetch and execute whatever the attacker is currently serving.

Malicious versions

2 flagged

6.0.57.2.8

Indicators of compromise (SHA-256)

424ebdaa04d4f7e8ce306f536421ac65d79467e73b05877caac6b72071bdaef9

6bd158a05893a55a82bee4867772aefbfb3199a443c38e7161db1a71d47ced86

Detection & response playbook

Backdoor / remote access

Find it
Search your lockfiles and build artifacts for chai-as-indexed (2 malicious versions).
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 installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. chai-as-indexed on npm has been identified as a malicious package (versions 6.0.5, 7.2.8 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-020191IN-MAL-2026-021118

References

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