Which versions of chai-promise-tools are malicious?

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

How do I remediate chai-promise-tools if I installed it?

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

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

Yes — chai-promise-tools is associated with the GHSA-2737-5rcq-jwmj, RLMA-2026-01180 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-promise-tools 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-promise-tools (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-promise-tools across your stack and pipelines.

Malicious package

chai-promise-toolsnpm

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

MAL-2026-677

Immediate action

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

npm uninstall chai-promise-tools

What this malware does

The package chai-promise-tools 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)

4406a20866edc56f03eff4272821c7993e0621588b95e3286ff4bf063216145b

8fbc46ec5143004a3a8dbf9138d7317efd21d323b0803a9c1c6f18b73f4ef7c6

e288a6b01935a2e48181dd40f2c1e9ce8bf4e2303f8753188a0324906613fd6e

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-promise-tools (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-promise-tools across your stack and pipelines.
If you installed it — respond
Remove chai-promise-tools 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-promise-tools 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-promise-tools 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-promise-tools 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-2737-5rcq-jwmjRLMA-2026-01180

References

github.com

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks chai-promise-tools-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