Which versions of lockedin-chai-chain are malicious?

The following npm versions of lockedin-chai-chain are flagged malicious: 1.2.6. Treat any of these as compromised.

How do I remediate lockedin-chai-chain if I installed it?

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

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

Yes — lockedin-chai-chain is associated with the RLMA-2026-05143, RLUA-2026-06310 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 lockedin-chai-chain across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for lockedin-chai-chain (version 1.2.6).

Malicious package

lockedin-chai-chainnpm

Advisory published Apr 15, 2026Updated Sep 1, 2026

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

Malicious code in lockedin-chai-chain (npm)

MAL-2026-2902

Immediate action

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

npm uninstall lockedin-chai-chain

What this malware does

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

The package lockedin-chai-chain was found to contain malicious code.

Malicious versions

1 flagged

1.2.6

Indicators of compromise (SHA-256)

5f043508b642cb099f524948847b7a4835d3646132e8728ce3ee38864f14b733

5073734fe3cb88eae1ae04a17854f30c8d6768e79ae90d8f12722e0531825942

55a668b5c54850bf94d5d6f81a4c21d56ace866526a3c1fdbce2c223536dc43d

Detection & response playbook

Backdoor / remote access

Find it
Search your lockfiles and build artifacts for lockedin-chai-chain (version 1.2.6).
If you installed it — respond
lockedin-chai-chain 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 lockedin-chai-chain 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. lockedin-chai-chain on npm has been identified as a malicious package (version 1.2.6 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2026-05143RLUA-2026-06310

References

Credits

Amazon Inspector · finder
ReversingLabs · finder
indece · finder

Detect & block this

O3 blocks lockedin-chai-chain-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