Which versions of chai-as-tested are malicious?

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

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

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

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

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

Search your lockfiles and build artifacts for chai-as-tested (version 2.3.8).

Malicious package

chai-as-testednpm

Advisory published Dec 23, 2025Updated Mar 19, 2026

chai-as-tested is a confirmed malicious npm package (MAL-2025-192723) that executes malicious code on install (malicious version 2.3.8). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in chai-as-tested (npm)

MAL-2025-192723

Immediate action

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

npm uninstall chai-as-tested

What this malware does

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

Malicious versions

1 flagged

2.3.8

Indicators of compromise (SHA-256)

71447cc344dc42af790f9ad77b843183fb20836b3891b04200718a433d5fd46c

cfbc69e8b6f340614b2fdd5378d7f730a4d79e03499a7e41b578028ad970e4eb

5932698a805e8f57e918215d4425927aba8ac22be67c0ac73e638d6e12035cd2

Detection & response playbook

Malicious package

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

Campaign

RLMA-2025-06084RLUA-2026-01159

References

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

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