MAL-2026-10630 Malicious code in chai-as-byte (npm)
Malicious package
Published
MAL-2026-10630 is a malicious package: chai-as-byte (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-10630/ (Markdown: https://insights.sbomify.com/MAL-2026-10630/index.md)
- Package
- chai-as-byte
- Registry
- npm
What is MAL-2026-10630?
MAL-2026-10630 is a malicious package in chai-as-byte, published on 15 Jul 2026.
Official description
On require of the package's main entry, index.js detaches a child process that runs lib/initializeCaller.js. That script posts the caller's entire process.env to a base64-obfuscated URL (decoded destination: https://ipcheck-hashed.vercel.app/api/auth/6c1d60d35852ef0c05df) using axios, then passes the response body to
new Function('require', response.data) and invokes it with the module require — giving the remote endpoint arbitrary code execution on the installer's host with full module access. The package name mimics the chai-as-* family while its metadata advertises a JSON logger, and neither role is implemented in the shipped code; the main entry silently spawns the exfil/RCE task instead of exposing any library API. The bulk-environment upload captures CI secrets, cloud tokens, and API keys that live in process.env in typical build environments.What should I do about MAL-2026-10630?
Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.