Which versions of chai-async-test are malicious?

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

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

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

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

Yes — chai-async-test is associated with the GHSA-wjj4-r47f-m9q8, RLMA-2026-01164 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-test 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-test (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-async-test across your stack and pipelines.

Malicious package

chai-async-testnpm

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

MAL-2026-409

Immediate action

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

npm uninstall chai-async-test

What this malware does

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

44653d8509702f49ad07480d256afe34186fa1f3920fca7b95d57ef1f7ed8552

d513c8edc24de9b9993282b15030364ac655c161954965840f5a8d630470cef1

9c4536a2c3ef9e98ffcf1cb33489f43d34ec489876ed0abb389c1df4d9f8ec99

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-test (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-async-test across your stack and pipelines.
If you installed it — respond
Remove chai-async-test 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-test 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-test 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-test 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-wjj4-r47f-m9q8RLMA-2026-01164

References

github.com

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

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