Which versions of chai-as-precision are malicious?

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

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

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

I already installed chai-as-precision — how do I know if it already compromised me?

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

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

Malicious package

chai-as-precisionnpm

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

MAL-2026-10219

Immediate action

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

npm uninstall chai-as-precision

What this malware does

Package is published as chai-as-precision but its shipped code mimics pino (exports middleware.pino, ships pino.js/proto.js/redaction.js), a name/purpose mismatch consistent with typosquatting or masquerade for transitive installation. When the exported middleware is invoked, index.js spawns node lib/initializeCaller.js with detached: true, stdio: 'ignore', and child.unref(), decoupling the child from the parent and suppressing output. lib/initializeCaller.js shadows process with a local object whose DEV_API_KEY is a base64 blob decoding to https://tomato-brunhilda-40.tiiny.site/index.json, GETs that URL, and executes the returned cookie field via new Function.constructor('require', response)(require) — arbitrary attacker-controlled JavaScript is executed with full require access on the host running the middleware. The destination is an anonymous tiiny.site host unrelated to any documented purpose, the URL and custom auth header are base64-hidden behind a fake env-var wrapper, and the executed content is mutable and controlled by whoever owns the tiiny.site page.

Malicious versions

1 flagged

7.0.6

Indicators of compromise (SHA-256)

f8b5d1218fae5d91755d8f9ca8ed37983e7d589c6fd88012d3ddb29a84a2cc56

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

Campaign

IN-MAL-2026-009791

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

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