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 ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.

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?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for chai-as-deploy (version 2.4.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging chai-as-deploy across your stack and pipelines.

Malicious package

chai-as-deploynpm

Malicious code in chai-as-deploy (npm) Remove it immediately and rotate any exposed credentials.

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
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for chai-as-deploy (version 2.4.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging chai-as-deploy across your stack and pipelines.
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 ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks chai-as-deploy before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.

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