Which versions of env-stream are malicious?

The following npm versions of env-stream are flagged malicious: 1.0.1, 1.0.2. Treat any of these as compromised.

How do I remediate env-stream if I installed it?

env-stream is a typosquat — you almost certainly intended a legitimately-named package. Remove env-stream, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.

I already installed env-stream — how do I know if it already compromised me?

If env-stream was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.

Is env-stream part of a known attack campaign?

Yes — env-stream is associated with the IN-MAL-2026-009844, IN-MAL-2026-009845 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find env-stream across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for env-stream (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging env-stream across your stack and pipelines.

Malicious package

env-streamnpm

Malicious code in env-stream (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-10412

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall env-stream

What this malware does

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.

Malicious versions

2 flagged

1.0.11.0.2

Indicators of compromise (SHA-256)

677d8eb3f7a80ffdc5f500d41f25b1f09415199e55e3194e96fe55b3c895111c

d5d06b9a9a214d1e08fd459bd98442bad75e003177590786d876b948a7329f11

Detection & response playbook

Typosquat

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for env-stream (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging env-stream across your stack and pipelines.
If you installed it — respond
env-stream is a typosquat — you almost certainly intended a legitimately-named package. Remove env-stream, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.
Did it already run?
If env-stream was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks env-stream before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.

Frequently asked questions

No. env-stream on npm has been identified as a malicious package (versions 1.0.1, 1.0.2 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-009844IN-MAL-2026-009845

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks env-stream-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

Malware detection Runtime egress monitoring