Which versions of chai-status are malicious?

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

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

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

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

Yes — chai-status is associated with the GHSA-wh9m-xqr4-wc75, RLMA-2025-06092, RLUA-2026-01191 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-status 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-status (version 2.4.2). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging chai-status across your stack and pipelines.

Malicious package

chai-statusnpm

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

MAL-2025-191546

Immediate action

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

npm uninstall chai-status

What this malware does

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

2.4.2

Indicators of compromise (SHA-256)

ac16fe9f8e1d6ef61aa920967a83f93dc57d69f70b534ac70a2e59870b2b3533

36f6f6dd537cdb195504efe77187096dff2f05e7ffd064975c9f54a4d45e17b9

bfa71fcd09a95d672d0fb6842e53d31fc2309da7652ec9fdb255546ac9c6c618

4ca910a0b89790bfd277faf857b9d3748e6926029dfe4b0bba497b929d3c7a64

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

Campaign

GHSA-wh9m-xqr4-wc75RLMA-2025-06092RLUA-2026-01191

References

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

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