Which versions of chai-as-tuned are malicious?

The following npm versions of chai-as-tuned are flagged malicious: 7.2.2. Treat any of these as compromised.

How do I remediate chai-as-tuned if I installed it?

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

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

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

Malicious package

chai-as-tunednpm

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

MAL-2026-4513

Immediate action

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

npm uninstall chai-as-tuned

What this malware does

Package name chai-as-tuned impersonates chai-as-promised and ships a README copy-pasted from the unrelated pino project (npm/CI badges point at pinojs/pino). The advertised middleware in index.js spawns lib/initializeCaller.js as a detached node process whenever the exported function is invoked. That script constructs a fake local process object whose DEV_API_KEY is a base64 literal decoding to https://aqua-margit-84.tiiny.site/index.json (tiiny.site is an anonymous static-hosting service), GETs the JSON via axios, and passes the response.cookie field to new Function.constructor('require', response)(require) — executing attacker-controlled JavaScript with full Node privileges and access to the host's require. The combination of name-confusion, copied README, base64-hidden C2 URL, Function.constructor indirection to defeat static review, and remote-fetch-and-eval is an unambiguous supply-chain attack: any consumer who follows the README and uses the main export will execute whatever code the attacker serves at runtime.

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

1 flagged

7.2.2

Indicators of compromise (SHA-256)

f7e00f81e117716cfd7fd3565cf8b04073cd494a6da2c23749669133806a7473

456afd075e2df98b9a07a876eb8b1e26cff0afe3f517d7b0f226f654e3e22bed

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 chai-as-tuned (version 7.2.2). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging chai-as-tuned across your stack and pipelines.
If you installed it — respond
chai-as-tuned 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-as-tuned 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-as-tuned 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. chai-as-tuned on npm has been identified as a malicious package (version 7.2.2 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-003965GHSA-2f37-mh3q-7394

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks chai-as-tuned-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