Which versions of chai-as-belonged are malicious?

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

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

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

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

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

Search your lockfiles and build artifacts for chai-as-belonged (version 4.3.8).

Malicious package

chai-as-belongednpm

Advisory published Jul 7, 2026Updated Sep 1, 2026

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

Malicious code in chai-as-belonged (npm)

MAL-2026-7231

Immediate action

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

npm uninstall chai-as-belonged

Malicious versions

1 flagged

4.3.8

Indicators of compromise (SHA-256)

84e02c580af1e8375ebd90d20329cea20674913bb5dd30b1c11865cefb1d2783

e4fa2a69e924e20c078501f6c0418d1e78111e90a0d9158fefb903bcd057336c

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-04977RLUA-2026-06108

References

Credits

ReversingLabs · finder

Detect & block this

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