Which versions of chai-as-deploy are malicious?

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

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

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

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

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

Search your lockfiles and build artifacts for chai-as-deploy (version 2.4.1).

Malicious package

chai-as-deploynpm

Advisory published Dec 23, 2025Updated Mar 19, 2026

chai-as-deploy is a confirmed malicious npm package (MAL-2025-192722) that executes malicious code on install (malicious version 2.4.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in chai-as-deploy (npm)

MAL-2025-192722

Immediate action

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

npm uninstall chai-as-deploy

What this malware does

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

Malicious versions

1 flagged

2.4.1

Indicators of compromise (SHA-256)

c2a2377ff0458c7dab6c3eca4e14a88b729d15442e668869a56773dc24ccf50e

6777d6fb72a2a1e304855ebdd4aa8f8e5e8410136ebcc580b71b5e5f4152eaf2

e73d8f915293f1a7e37751ab5a000de0583bfc62a154b3769f6804f03975e0ce

Detection & response playbook

Malicious package

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

Campaign

RLMA-2025-06082RLUA-2026-01145

References

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

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