MAL-2026-4514 Malicious code in chai-as-vite (npm)
Malicious package
Published
MAL-2026-4514 is a malicious package: chai-as-vite (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-4514/ (Markdown: https://insights.sbomify.com/MAL-2026-4514/index.md)
- Package
- chai-as-vite
- Registry
- npm
What is MAL-2026-4514?
MAL-2026-4514 is a malicious package in chai-as-vite, published on 21 May 2026.
Official description
The package masquerades as a pino-style logger (exports
module.exports.pino = middleware, keywords fast,logger,stream,json, lib filenames proto.js, redaction.js, multistream.js, transport.js) under a name evoking chai/vite tooling. When a consumer requires the package and invokes the exported middleware, lib/initializeCaller.js is launched as a detached node child process. That script defines a local process shadow whose env holds base64 strings (DEV_API_KEY, DEV_SECRET_KEY, DEV_SECRET_VALUE), atob-decodes them to recover the URL https://purple-kelila-79.tiiny.site/data.json and the header x-secret-key: _, fetches the response via axios, then executes the response body with new Function.constructor('require', response)(require) — full arbitrary code execution with require access on the installer's machine, with retry. The destination is an anonymous, mutable tiiny.site host with no version pinning and no integrity check, so the operator can rotate the delivered payload at will. Base64-encoded URL and header values, the fake process.env shadow, and the detached child-process launch are intentional evasion.What should I do about MAL-2026-4514?
Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.