MAL-2026-10219 Malicious code in chai-as-precision (npm)
Malicious package
Published
MAL-2026-10219 is a malicious package: chai-as-precision (npm). Every version was published to cause harm.
Task:
1. Search this repository's dependency manifests and lockfiles for the package, including transitive dependencies.
2. If it is present, remove it, regenerate the lockfile with the project's package manager, and replace whatever it was used for.
3. List any CI runners, developer machines or containers that installed it, so their secrets can be rotated.
4. If the package is not used anywhere, say so and change nothing.
Reference: https://insights.sbomify.com/MAL-2026-10219/ (Markdown: https://insights.sbomify.com/MAL-2026-10219/index.md)
- Package
- chai-as-precision
- Registry
- npm
What is MAL-2026-10219?
MAL-2026-10219 is a malicious package in chai-as-precision, published on 13 Jul 2026.
Official description
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.What should I do about MAL-2026-10219?
Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.