MAL-2026-10412 Malicious code in env-stream (npm)
Malicious package
Published
MAL-2026-10412 is a malicious package: env-stream (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-10412/ (Markdown: https://insights.sbomify.com/MAL-2026-10412/index.md)
- Package
- env-stream
- Registry
- npm
What is MAL-2026-10412?
MAL-2026-10412 is a malicious package in env-stream, published on 13 Jul 2026.
Official description
Package publishes under the name
env-stream but its package.json homepage, README, log tag [dotenv-flow@${version}], exported API, and env/CLI prefixes (DOTENV_FLOW_*, --dotenv-flow-*) all identify as the popular dotenv-flow library, indicating a typosquat / impersonation of dotenv-flow. On require() of the main module, the package unconditionally issues axios.get() against a hardcoded remote endpoint at https://realase-0626.vercel.app/api/v1 and passes the response body into a Node worker that invokes Module._compile(responseBody, 'error.js') and returns m.exports() to the parent. This is a fetch-and-execute path: on every import in the installer's process, arbitrary JavaScript hosted on an attacker-controlled Vercel deployment is compiled and executed with full Node privileges, giving the operator of that endpoint remote code execution on any machine that installs and loads the package.What should I do about MAL-2026-10412?
Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.