Which versions of chai-tests-async are malicious?

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

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

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

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

Yes — chai-tests-async is associated with the GHSA-cprx-7wv5-xx9f, RLMA-2026-01195 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-tests-async 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-tests-async (version 3.3.5). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging chai-tests-async across your stack and pipelines.

Malicious package

chai-tests-asyncnpm

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

MAL-2026-172

Immediate action

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

npm uninstall chai-tests-async

What this malware does

The package chai-tests-async 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

3.3.5

Indicators of compromise (SHA-256)

dcf794e17cf7abc4b2cb2473da8d9425c720cdcf72e279adab300048154cd638

8b1116b21de9a6d4e20096c4af06f91c10ce3eaadd3d722923988084ddd4899a

31f8c24b41d7960125fb254fb6ac5f2221921747e5a7c2f114105be44088723e

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-tests-async (version 3.3.5). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging chai-tests-async across your stack and pipelines.
If you installed it — respond
Remove chai-tests-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-tests-async 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-tests-async 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-tests-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

GHSA-cprx-7wv5-xx9fRLMA-2026-01195

References

github.com

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks chai-tests-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