Which versions of chai-async-chain are malicious?

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

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

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

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

Yes — chai-async-chain is associated with the GHSA-9c7f-644c-p3xw, RLMA-2025-06086 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-chain 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-chain (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-async-chain across your stack and pipelines.

Malicious package

chai-async-chainnpm

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

MAL-2025-190627

Immediate action

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

npm uninstall chai-async-chain

What this malware does

The package chai-async-chain 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.1

Indicators of compromise (SHA-256)

fdec53906ddd8f960924b6b45b6c8a742115debcec85495bd0f052d7d13105ec

e99ef9605c8341ad648b4f6fb3d4102c0288cf3742d3e1abe55c1d45d9fcdbec

0d5220f0e61ec87bba00a411e021d994b4cd8e91ff78c250ee3fd28d87b4dfc5

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-chain (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-async-chain across your stack and pipelines.
If you installed it — respond
Remove chai-async-chain 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-chain 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-chain 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-chain 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

GHSA-9c7f-644c-p3xwRLMA-2025-06086

References

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

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