Which versions of chai-as-absorbed are malicious?

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

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

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

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

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

Search your lockfiles and build artifacts for chai-as-absorbed (version 3.4.1).

Malicious package

chai-as-absorbednpm

Advisory published Jul 7, 2026Updated Sep 1, 2026

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

Malicious code in chai-as-absorbed (npm)

MAL-2026-7230

Immediate action

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

npm uninstall chai-as-absorbed

Malicious versions

1 flagged

3.4.1

Indicators of compromise (SHA-256)

7d2cfd118cf8fac7f432e43ea04afe2bd2eeaea721d3963d172c4beb231aeeb0

38c4d956cd440b9afa66efaeb5b520fefd65cbd24ec2efbb75f57a93e5e553e3

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-04975RLUA-2026-06105

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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