Which versions of chai-async-chains are malicious?

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

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

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

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

Yes — chai-async-chains is associated with the GHSA-r8fq-6pxg-2f6q, RLMA-2026-01162 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-async-chains 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-async-chains (version 2.4.2). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging chai-async-chains across your stack and pipelines.

Malicious package

chai-async-chainsnpm

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

MAL-2025-192753

Immediate action

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

npm uninstall chai-async-chains

What this malware does

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

Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

Malicious versions

1 flagged

2.4.2

Indicators of compromise (SHA-256)

71f001d60e21257b0a14e3048d80541eabe69df7b151f61ee5e3c57a036ddd94

3dfd7db9210fae054def8abcb6989e1158a4774dbec18c08ac6eebcbf95ef753

d5a17e754026493435c5568162082db5e2e730b15c151bbc1f55c3b5b7b15b65

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-async-chains (version 2.4.2). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging chai-async-chains across your stack and pipelines.
If you installed it — respond
Remove chai-async-chains 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-async-chains 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-async-chains 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-async-chains on npm has been identified as a malicious package (version 2.4.2 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-r8fq-6pxg-2f6qRLMA-2026-01162

References

github.com

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

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