Which versions of chai-as-informed are malicious?

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

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

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

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

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

Search your lockfiles and build artifacts for chai-as-informed (version 1.2.0).

Malicious package

chai-as-informednpm

Advisory published Jul 7, 2026Updated Sep 1, 2026

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

Malicious code in chai-as-informed (npm)

MAL-2026-7234

Immediate action

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

npm uninstall chai-as-informed

Malicious versions

1 flagged

1.2.0

Indicators of compromise (SHA-256)

eb3164ee133065bfa8e9fa82b1701547df00c1b2410ecff2c62b241b77ff73ac

41c1232070030e7db32c2787bf45b9891c8ec1decc073df6a2fb0884163a7020

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-04988RLUA-2026-06116

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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