Which versions of chai-as-purified are malicious?

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

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

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

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

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

Search your lockfiles and build artifacts for chai-as-purified (version 7.1.1).

Malicious package

chai-as-purifiednpm

Advisory published Jul 7, 2026Updated Sep 1, 2026

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

Malicious code in chai-as-purified (npm)

MAL-2026-7238

Immediate action

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

npm uninstall chai-as-purified

Malicious versions

1 flagged

7.1.1

Indicators of compromise (SHA-256)

af267806c76716d2cb8e352725f91960e294795c5b7c13a2c8f96bb53df0bc00

8d25d1038f7e92fb2aeed1518ff0619a9cfd7e1b3d82441a735795cee233060b

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-04994RLUA-2026-06123

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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