chai-use-chainsnpm
Malicious code in chai-use-chains (npm) Remove it immediately and rotate any exposed credentials.
What this malware does
chai-use-chains 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 chai-use-chains was found to contain malicious code.
Malicious versions
Every published version of this package is considered malicious — remove it entirely.
Indicators of compromise (SHA-256)
Detection & response playbook
Backdoor / remote accessFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for chai-use-chains (all published versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging chai-use-chains across your stack and pipelines.
If you installed it — respond
chai-use-chains 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-use-chains 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-use-chains 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
References
Credits
- Amazon Inspector · finder
- indece · finder
Detect & block this
O3 blocks chai-use-chains-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the C2 callback and severs the channel.