Which versions of dotenv-runtime are malicious?

The following npm versions of dotenv-runtime are flagged malicious: 1.0.0. Treat any of these as compromised.

How do I remediate dotenv-runtime if I installed it?

Remove dotenv-runtime from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

I already installed dotenv-runtime — how do I know if it already compromised me?

If dotenv-runtime was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Is dotenv-runtime part of a known attack campaign?

Yes — dotenv-runtime is associated with the IN-MAL-2026-021117 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 dotenv-runtime across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for dotenv-runtime (version 1.0.0).

Malicious package

dotenv-runtimenpm

Advisory published Oct 8, 2026Updated Oct 8, 2026

dotenv-runtime is a confirmed malicious npm package (MAL-2026-17657) that executes malicious code on install (malicious version 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in dotenv-runtime (npm)

MAL-2026-17657

Immediate action

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

npm uninstall dotenv-runtime

What this malware does

The package presents itself as a dotenv parser but on require() index.cjs calls a function named dispatchAnalytics() that reads dist/stest.jpg, extracts a hidden string from the JPEG APP13 EXIF segment, writes a relay_*.vbs file to the OS temp directory, and spawns it detached via wscript.exe. The VBS invokes powershell.exe with a base64-encoded command that downloads a Windows executable from https://hardwood-studio-obviously-briefing.trycloudflare.com/download/winhost and starts it hidden. A second shipped file dist/decode.js is a heavily obfuscated loader that RC4-decrypts a base64 blob and executes the result via new Function(require, module, __filename, __dirname, <decoded>), providing a secondary dynamic-code sink. The bundled package.json embedded inside dist/cli.cjs self-identifies as [email protected], while the published package name is [email protected] — a repackaged dotenv look-alike. The dispatchAnalytics name and the stest.jpg filename are cover for the dropper chain.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

50639fcdb3317812a161b8f54fbf22d2565881af534da0d2ec8f7d37ecbd3f3b

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for dotenv-runtime (version 1.0.0).
If you installed it — respond
Remove dotenv-runtime from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If dotenv-runtime was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. dotenv-runtime on npm has been identified as a malicious package (version 1.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-021117

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks dotenv-runtime-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

Explore

All malware advisories How O3 detects malware Vulnerability database