Which versions of chai-beta are malicious?

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

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

chai-beta establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.

I already installed chai-beta — how do I know if it already compromised me?

If chai-beta was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Is chai-beta part of a known attack campaign?

Yes — chai-beta is associated with the RLMA-2026-05004, RLUA-2026-06134 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-beta across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for chai-beta (version 1.1.9).

Malicious package

chai-betanpm

Advisory published Apr 15, 2026Updated Sep 1, 2026

chai-beta is a confirmed malicious npm package (MAL-2026-2897) that opens a backdoor for remote access (malicious version 1.1.9). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in chai-beta (npm)

MAL-2026-2897

Immediate action

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

npm uninstall chai-beta

What this malware does

chai-beta is a malicious npm package that when imported downloads a C2 dropper from https://jsonkeeper[.]com/b/XRGF3 and executes it (similar to malware in to chai-await-test).

The package chai-beta was found to contain malicious code.

Malicious versions

1 flagged

1.1.9

Indicators of compromise (SHA-256)

b57727c6a080ac8eccf4106639fc8fceab20fd4fb96142c8a8cb9b68422d4867

3eb41b2c6b5a301a28377d83c35161308b92697cce0171d2a780702899796fe8

d397c0c1cf7127cd166f25afdebdfac6261ebc36e5fa055a1350c000acec3a73

Detection & response playbook

Backdoor / remote access

Find it
Search your lockfiles and build artifacts for chai-beta (version 1.1.9).
If you installed it — respond
chai-beta establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.
Did it already run?
If chai-beta was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. chai-beta on npm has been identified as a malicious package (version 1.1.9 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2026-05004RLUA-2026-06134

References

Credits

Amazon Inspector · finder
ReversingLabs · finder
indece · finder

Detect & block this

O3 blocks chai-beta-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the C2 callback and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database