Which versions of chai-as-attached are malicious?

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

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

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

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

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

Search your lockfiles and build artifacts for chai-as-attached (version 1.4.5).

Malicious package

chai-as-attachednpm

Advisory published Mar 24, 2026Updated Apr 7, 2026

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

Malicious code in chai-as-attached (npm)

MAL-2026-2338

Immediate action

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

npm uninstall chai-as-attached

What this malware does

The package chai-as-attached was found to contain malicious code.

Malicious versions

1 flagged

1.4.5

Indicators of compromise (SHA-256)

21b652298a9e1e8b63415de7e5b90b47ee909303cd5843b5db16aef648511aab

f3334b8d2a1f3861b1427af8ae49ac714b72ab19d6a571835e6c84c5d4b83b1a

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-01716

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

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