Which versions of chai-max are malicious?

The following npm versions of chai-max are flagged malicious: 2.4.2, 2.4.3. Treat any of these as compromised.

How do I remediate chai-max if I installed it?

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

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

Yes — chai-max is associated with the GHSA-cgcm-g6p8-2xxm, RLMA-2026-01177 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-max 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-max (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging chai-max across your stack and pipelines.

Malicious package

chai-maxnpm

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

MAL-2025-192754

Immediate action

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

npm uninstall chai-max

What this malware does

The package chai-max 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

2 flagged

2.4.22.4.3

Indicators of compromise (SHA-256)

a6e46cc56f071a0c9f8afeaa19cf981997f743503c55a5e155fd1c99bf53d3a4

1bf9b30832b678dc77fdae0e722638e2a3ff7ba5cf07b09960233418192dd073

949471d39b83cbed6d6a39712a9a915353a62d57fef8d72b0f750dfe336ed16d

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-max (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging chai-max across your stack and pipelines.
If you installed it — respond
Remove chai-max 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-max 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-max 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-max on npm has been identified as a malicious package (versions 2.4.2, 2.4.3 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-cgcm-g6p8-2xxmRLMA-2026-01177

References

github.com

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

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