Which versions of chai-as-sai are malicious?

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

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

Remove chai-as-sai from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

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

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

Yes — chai-as-sai is associated with the RLMA-2026-04998, RLUA-2026-06125 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-sai across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for chai-as-sai (version 2.3.5).

Malicious package

chai-as-sainpm

Advisory published Jul 7, 2026Updated Sep 1, 2026

chai-as-sai is a confirmed malicious npm package (MAL-2026-7239) that executes malicious code on install (malicious version 2.3.5). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in chai-as-sai (npm)

MAL-2026-7239

Immediate action

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

npm uninstall chai-as-sai

Malicious versions

1 flagged

2.3.5

Indicators of compromise (SHA-256)

d9bbb7325467de3f6947977fbf5f3e87fea3ec2714c67f578521592c07771c8b

c086c02df0594dc15c91fcc216143a698059ad9872405a76d7de12daa702abd7

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for chai-as-sai (version 2.3.5).
If you installed it — respond
Remove chai-as-sai from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If chai-as-sai 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-sai on npm has been identified as a malicious package (version 2.3.5 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2026-04998RLUA-2026-06125

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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