Which versions of chai-cli-async are malicious?

The following npm versions of chai-cli-async are flagged malicious: 3.3.5. Treat any of these as compromised.

How do I remediate chai-cli-async if I installed it?

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

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

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

Search your lockfiles and build artifacts for chai-cli-async (version 3.3.5).

Malicious package

chai-cli-asyncnpm

Advisory published Mar 18, 2026Updated Mar 23, 2026

chai-cli-async is a confirmed malicious npm package (MAL-2026-1677) that executes malicious code on install (malicious version 3.3.5). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in chai-cli-async (npm)

MAL-2026-1677

Immediate action

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

npm uninstall chai-cli-async

What this malware does

The package chai-cli-async was found to contain malicious code.

Malicious versions

1 flagged

3.3.5

Indicators of compromise (SHA-256)

4cb93d91fb6085387e054d4f882822058196ca88a3e49a99e06fab37e6565863

1d9f4be84db26d0ce71d5bcfda424b1af08abddc37c23d3a2ef2b4263534fde2

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-01172

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks chai-cli-async-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