Which versions of chai-as-test are malicious?

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

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

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

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

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

Search your lockfiles and build artifacts for chai-as-test (version 1.2.9).

Malicious package

chai-as-testnpm

Advisory published Jul 7, 2026Updated Sep 1, 2026

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

Malicious code in chai-as-test (npm)

MAL-2026-7240

Immediate action

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

npm uninstall chai-as-test

Malicious versions

1 flagged

1.2.9

Indicators of compromise (SHA-256)

6b81a2f6a7e2c918885bbe8b7e6b797bf7f11d9af318b4cf940cb26216c70453

08426da56479ddf7a9491aa4675ded163db0f279640fbc53f28890845d8a3628

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-05000RLUA-2026-06130

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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