MAL-2026-10040 Malicious code in chai-as-balanced (npm)
Malicious package
Published
MAL-2026-10040 is a malicious package: chai-as-balanced (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-10040/ (Markdown: https://insights.sbomify.com/MAL-2026-10040/index.md)
- Package
- chai-as-balanced
- Registry
- npm
What is MAL-2026-10040?
MAL-2026-10040 is a malicious package in chai-as-balanced, published on 9 Jul 2026.
Official description
chai-as-balanced is a typosquat of chai-as-promised (also impersonating pino via README/badges/exports) that ships a remote code execution dropper. lib/const.js defines a fake process.env object whose DEV_API_KEY value is a base64-encoded URL to api.jsonstorage.net (an anonymous, attacker-mutable JSON storage service). lib/caller.js base64-decodes that URL, GETs the JSON blob using an obfuscated x-secret-key header, extracts the
cookie field, and executes it via new Function.constructor('require', s)(require) — granting the fetched payload full Node privileges and access to the real require. index.js triggers this by spawning lib/caller.js as a detached, stdio-ignored child with child.unref(), so the dropper runs in the background and outlives the parent invocation, concealing execution from the caller. Because the payload source is anonymous and mutable, the executed code can change at any time without a new package release. Installers who mistype chai-as-promised as chai-as-balanced and invoke the exported middleware receive arbitrary attacker-controlled code execution.What should I do about MAL-2026-10040?
Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.