Which versions of chai-as-patched are malicious?

The following npm versions of chai-as-patched are flagged malicious: 7.0.5, 7.0.6. Treat any of these as compromised.

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

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

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

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

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

Malicious package

chai-as-patchednpm

Advisory published Jul 7, 2026Updated Sep 1, 2026

chai-as-patched is a confirmed malicious npm package (MAL-2026-7237) that executes malicious code on install (malicious versions 7.0.5, 7.0.6). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in chai-as-patched (npm)

MAL-2026-7237

Immediate action

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

npm uninstall chai-as-patched

Malicious versions

2 flagged

7.0.57.0.6

Indicators of compromise (SHA-256)

808b58945aa8e3835626715f3efd302707113e08a4254dfc415270d1fc7d0b2b

fb33ad0f8d7a8238fe3add8e6095d3d42ffa3bb50c205b3e690b7b0d33767352

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-04993RLUA-2026-06121

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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