Which versions of chai-as-refined are malicious?

The following npm versions of chai-as-refined are flagged malicious: 7.0.1, 7.0.2. Treat any of these as compromised.

How do I remediate chai-as-refined if I installed it?

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

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

Yes — chai-as-refined is associated with the GHSA-4jgh-4hh7-rpfj, RLMA-2026-01915 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-as-refined 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-as-refined (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-as-refined across your stack and pipelines.

Malicious package

chai-as-refinednpm

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

MAL-2026-2641

Immediate action

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

npm uninstall chai-as-refined

What this malware does

The package chai-as-refined 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

7.0.17.0.2

Indicators of compromise (SHA-256)

5a69e4e0dbfe130a3d5da8413eb7ad9a490dc1874ee69ef385156479b365da44

8d2f79dd547aa18fc452763d830bb97027a3b10f01076839123b2bd3c3c99f22

dc7bd5b01fccd5ef5cc96d9a4eecf5801c6b34a062718a2131d2b2abb7a93191

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-as-refined (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-as-refined across your stack and pipelines.
If you installed it — respond
Remove chai-as-refined 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-as-refined 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-as-refined 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-as-refined on npm has been identified as a malicious package (versions 7.0.1, 7.0.2 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-4jgh-4hh7-rpfjRLMA-2026-01915

References

github.com

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks chai-as-refined-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