Which versions of chai-as-chayn are malicious?

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

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

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

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

Yes — chai-as-chayn is associated with the GHSA-9mp5-2jp4-wmww, RLMA-2026-01718, RLUA-2026-01911 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-chayn 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-chayn (version 2.3.5). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging chai-as-chayn across your stack and pipelines.

Malicious package

chai-as-chaynnpm

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

MAL-2026-1975

Immediate action

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

npm uninstall chai-as-chayn

What this malware does

The package chai-as-chayn 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.3.5

Indicators of compromise (SHA-256)

57e4b17532a62987684bdd644c433a1aa7c4955324bb06eb3c6f7ed702fa0ed3

37e4fe08f70ebcaf1ebc9988e7ad2694a3b9708734e8623adcf930d1803bb72a

b429b9ae28b69c06edd8f392bff99296f6fa0cad1b87a9cc662655390f057165

e62230db83d400eb1cf8892bf8f783993a69fda5d67bf26f44e519fabd685d82

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

Campaign

GHSA-9mp5-2jp4-wmwwRLMA-2026-01718RLUA-2026-01911

References

github.com

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

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