Which versions of chai-as-chains are malicious?

The following npm versions of chai-as-chains are flagged malicious: 1.2.4, 1.2.7, 1.2.8. Treat any of these as compromised.

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

Remove chai-as-chains 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-chains — how do I know if it already compromised me?

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

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

Search your lockfiles and build artifacts for chai-as-chains (3 malicious versions).

Malicious package

chai-as-chainsnpm

Advisory published Mar 24, 2026Updated Sep 1, 2026

chai-as-chains is a confirmed malicious npm package (MAL-2026-2339) that executes malicious code on install (malicious versions 1.2.4, 1.2.7, 1.2.8). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in chai-as-chains (npm)

MAL-2026-2339

Immediate action

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

npm uninstall chai-as-chains

What this malware does

The package chai-as-chains was found to contain malicious code.

Malicious versions

3 flagged

1.2.41.2.71.2.8

Indicators of compromise (SHA-256)

7f8ba179a67a575e55b370c591be26055c8f2528382e11880ef147cec6a01cb1

abf6eaadbaedff56f824c4c68f8af9138c01d40189e0225051d35c52dee1adc9

58e7e56e2ca03a4c07554b7a3f08fb891991baffc564ce3ffea747332581ca1f

795a3fc2d008713072b5fdb11088abd8c9672daac4beaa586510ebb9f8ec7dd3

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for chai-as-chains (3 malicious versions).
If you installed it — respond
Remove chai-as-chains 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-chains 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-chains on npm has been identified as a malicious package (versions 1.2.4, 1.2.7, 1.2.8 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2026-01717RLUA-2026-04980RLUA-2026-06111

References

github.com

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

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