Which versions of chai-as-commited are malicious?

The following npm versions of chai-as-commited are flagged malicious: 2.38.8, 2.38.9. Treat any of these as compromised.

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

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

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

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

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

Malicious package

chai-as-commitednpm

Advisory published Jul 7, 2026Updated Sep 1, 2026

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

Malicious code in chai-as-commited (npm)

MAL-2026-7232

Immediate action

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

npm uninstall chai-as-commited

Malicious versions

2 flagged

2.38.82.38.9

Indicators of compromise (SHA-256)

c34d35b3af3ca614f7b7be01e7d1df0266f9df6a265756caea893e327bdbd077

37e6cfd4c0855af480d439bc88bfb7893b65a9a124dd6e2717e74575be8e105a

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-04982RLUA-2026-06112

References

Credits

ReversingLabs · finder

Detect & block this

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