Which versions of chai-as-legit are malicious?

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

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

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

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

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

Search your lockfiles and build artifacts for chai-as-legit (version 7.2.3).

Malicious package

chai-as-legitnpm

Advisory published Jul 7, 2026Updated Sep 1, 2026

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

Malicious code in chai-as-legit (npm)

MAL-2026-7236

Immediate action

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

npm uninstall chai-as-legit

Malicious versions

1 flagged

7.2.3

Indicators of compromise (SHA-256)

64d5f37980c227277e9d584ec60b446d048e28d47676df126e2891bcf6a163dc

eccf92c054add1484f63ca74550286f3d37e3c29f5bbc323944a950305f59eaf

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-04991RLUA-2026-06119

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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