Which versions of chain-chai-await are malicious?

The following npm versions of chain-chai-await are flagged malicious: 1.3.5, 1.3.6, 1.3.7. Treat any of these as compromised.

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

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

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

Yes — chain-chai-await is associated with the IN-MAL-2026-009130, IN-MAL-2026-009131, IN-MAL-2026-009135 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 chain-chai-await 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 chain-chai-await (3 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging chain-chai-await across your stack and pipelines.

Malicious package

chain-chai-awaitnpm

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

MAL-2026-10056

Immediate action

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

npm uninstall chain-chai-await

What this malware does

The package presents itself as a pino-compatible logger (exports pino, mirrors pino's lib/ layout with proto.js/redaction.js/transport.js/multistream.js/levels.js/time.js/symbols.js, and copies pino's defaultOptions shape) but has no relationship to the real pino package. When a consumer requires the package and invokes the exported middleware factory, index.js spawns lib/caller.js as a detached Node subprocess. caller.js performs an axios GET to https://jsonkeeper.com/b/K80JD, reads the cookie field from the JSON response, and executes it via new Function.constructor("require", s)(require) — arbitrary remote code execution in the consumer's Node process with full access to require. The fetch is retried up to 5 times. lib/const.js additionally stores a base64-encoded backup endpoint (aHR0cHM6Ly9qc29ua2VlcGVyLmNvbS9iL1pLNDVK → https://jsonkeeper.com/b/ZK45J) and base64-encoded header key/value (x-secret-key, _) used by the loader. The pino cover story, mirrored file layout, obfuscated backup URL, and remote-fetch-and-execute primitive against a public paste-like host are the fingerprint of a dropper disguised as a logging library.

Malicious versions

3 flagged

1.3.51.3.61.3.7

Indicators of compromise (SHA-256)

0b75f72f341a3e6ab70047551fd2ecad4fb8fe619395cab5017f95b124594ade

53dc585524bcc3e64a107006ba8c763591b071bb174c7acadd716b6e99ac1c34

8b950bcb8ad2c8f74739a2958be5c2b3121292e61c997fca332449a12dab2585

Detection & response playbook

Backdoor / remote access

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for chain-chai-await (3 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging chain-chai-await across your stack and pipelines.
If you installed it — respond
chain-chai-await 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 chain-chai-await 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 chain-chai-await 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. chain-chai-await on npm has been identified as a malicious package (versions 1.3.5, 1.3.6, 1.3.7 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-009130IN-MAL-2026-009131IN-MAL-2026-009135

References

Credits

Amazon Inspector · finder

Detect & block this

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