chai-mocksnpm
chai-mocks is a confirmed malicious npm package (MAL-2026-5306) that opens a backdoor for remote access (malicious version 1.1.5). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in chai-mocks (npm)
What this malware does
The package masquerades as a pino-style logger middleware but is a remote code loader. When the exported middleware is invoked, index.js spawns a detached node./lib/caller.js child process. caller.js fetches https://jsonkeeper.com/b/U2BTS (with a second URL https://jsonkeeper.com/b/XRGF3 stored base64-encoded in a variable named DEV_API_KEY to disguise it as a configuration constant), reads the cookie field of the JSON response, and executes it via new Function.constructor('require', s)(require) — arbitrary attacker-controlled code execution with full Node require access on the consumer's machine. jsonkeeper.com is an anonymous, mutable paste service; the contents can be changed by the author at any time without republishing the package. The package name (chai-mocks) and bait API surface (exports pino, references DEFAULT_LEVELS/redact/customLevels, scripts named smoke:pino) are unrelated to the package's author identity (Alexus111 [email protected]) and are designed to lure developers who mistype or confuse it with the chai or pino logger ecosystems. The base64-obfuscated URLs and fake DEV_API_KEY/DEV_SECRET_KEY variable names confirm intent to hide the C2 endpoint.
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
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-mocks (version 1.1.5). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging chai-mocks across your stack and pipelines.
If you installed it — respond
chai-mocks 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-mocks 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-mocks 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
Campaign
References
Credits
- Amazon Inspector · finder
Detect & block this
O3 blocks chai-mocks-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the C2 callback and severs the channel.