Which versions of chain-chai-async are malicious?

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

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

chain-chai-async is a typosquat — you almost certainly intended a legitimately-named package. Remove chain-chai-async, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.

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

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

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

Malicious package

chain-chai-asyncnpm

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

MAL-2026-10055

Immediate action

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

npm uninstall chain-chai-async

What this malware does

[email protected] impersonates the pino logging library (README badge links to npm/pino, exports module.exports.pino = middleware, and ships files copied from the real pino source tree). Its exported middleware factory in index.js spawns lib/caller.js as a detached child node process with stdio ignored, decoupling the payload from the parent's lifecycle and suppressing its output. lib/caller.js issues an HTTPS GET to https://jsonkeeper.com/b/EXSIF, extracts the cookie field from the JSON response, and passes it to new Function.constructor('require', s)(require) — executing attacker-controlled JavaScript with full Node require access on any machine that loads and invokes the package. The remote source is a mutable, unauthenticated paste service, so the executed code can be swapped at any time by the attacker without republishing the package. Any consumer who installs this package believing it to be pino and calls its exported middleware will trigger arbitrary remote code execution on the host.

Malicious versions

1 flagged

1.3.5

Indicators of compromise (SHA-256)

655c64cb99f74a3b96f1b5e1d0102ce0c756e63368a5ca252e70e49e98f346b3

Detection & response playbook

Typosquat

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for chain-chai-async (version 1.3.5). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging chain-chai-async across your stack and pipelines.
If you installed it — respond
chain-chai-async is a typosquat — you almost certainly intended a legitimately-named package. Remove chain-chai-async, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.
Did it already run?
If chain-chai-async 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-async 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-async on npm has been identified as a malicious package (version 1.3.5 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-009138

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks chain-chai-async-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

Malware detection Runtime egress monitoring