Which versions of chai-as-upgraded are malicious?

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

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

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

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

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

Search your lockfiles and build artifacts for chai-as-upgraded (version 7.0.5).

Malicious package

chai-as-upgradednpm

Advisory published Jul 7, 2026Updated Sep 1, 2026

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

Malicious code in chai-as-upgraded (npm)

MAL-2026-7241

Immediate action

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

npm uninstall chai-as-upgraded

Malicious versions

1 flagged

7.0.5

Indicators of compromise (SHA-256)

7036528f196315d7e7fbe2d58044e6903baee0547f7b49d63522edb273a7b401

4bc628c5823723c270e14e0568c7388cf40b170342138ad4c521fe50623243ba

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-05002RLUA-2026-06132

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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