Which versions of chai-await-cli are malicious?

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

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

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

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

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

Search your lockfiles and build artifacts for chai-await-cli (version 2.3.5).

Malicious package

chai-await-clinpm

Advisory published Mar 18, 2026Updated Mar 23, 2026

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

Malicious code in chai-await-cli (npm)

MAL-2026-1674

Immediate action

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

npm uninstall chai-await-cli

What this malware does

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

Malicious versions

1 flagged

2.3.5

Indicators of compromise (SHA-256)

acdec8b9addc9abb94b9fc7fe8de3f8a04190b2f09359348046bc02a6be55ad5

eba2ac08d1a163026221030089df15f1e10a15be587c27714e659f4a98ec51bf

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-01167

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

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