Which versions of chai-async-tests are malicious?

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

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

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

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

Yes — chai-async-tests is associated with the GHSA-7rw2-vmhh-r49r, RLMA-2026-01165 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-tests 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-tests (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-tests across your stack and pipelines.

Malicious package

chai-async-testsnpm

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

MAL-2026-585

Immediate action

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

npm uninstall chai-async-tests

What this malware does

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

4303ac7ff339f51dfbc53ed8c70cd02a76123b62e0448bca935128fd313ab33e

9fe54f3f00b12c9b57fd672be7ddbe4a46342c24fe308c31f31c6156ae436d8b

36c5eaf2b3be2123db6cfc1019b18fd09d6be64bc043a9f0d74158ff3c9f7a29

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-tests (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-tests across your stack and pipelines.
If you installed it — respond
Remove chai-async-tests 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-tests 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-tests 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-tests 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-7rw2-vmhh-r49rRLMA-2026-01165

References

github.com

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

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