MAL-2026-6994 Malicious code in chai-presentation (npm)
Malicious package
Published
MAL-2026-6994 is a malicious package: chai-presentation (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-6994/ (Markdown: https://insights.sbomify.com/MAL-2026-6994/index.md)
- Package
- chai-presentation
- Registry
- npm
What is MAL-2026-6994?
MAL-2026-6994 is a malicious package in chai-presentation, published on 8 Jul 2026.
Official description
On require(), index.js issues an HTTPS GET to https://www.jsonkeeper.com/b/PC5CK and passes the response's
cookie field to new Function('require',...), immediately invoking it with the host's require. This gives whoever controls that jsonkeeper.com paste full Node.js execution privileges on the installer's machine the moment any consumer imports the package. A second staged loader is wired in parallel: index.js top-level spawns a detached, stdio-ignored Node child running lib/caller.js, which polls a URL built from config values and, on a 404 response, passes error.response.data.token to Function.constructor and executes it with require. lib/const.js additionally stores a base64 string under DEV_API_KEY that decodes to https://jsonkeeper.com/b/4NAKK — a second anonymous paste-host URL hidden from plain-string scanning. The package name presents as a chai plugin but the README describes an unrelated package (chai-submission), and declared dependencies (axios, request, sqlite3) are unrelated to chai assertions — an impersonation lure wrapping two import-time remote-eval channels.What should I do about MAL-2026-6994?
Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.