Which versions of dotenv-native are malicious?

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

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

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

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

If dotenv-native 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 dotenv-native part of a known attack campaign?

Yes — dotenv-native is associated with the IN-MAL-2026-020614 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-native 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 dotenv-native (version 1.0.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging dotenv-native across your stack and pipelines.

Malicious package

dotenv-nativenpm

dotenv-native is a confirmed malicious npm package (MAL-2026-17231) that typosquats a legitimate package to trick installs (malicious version 1.0.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in dotenv-native (npm)

MAL-2026-17231

Immediate action

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

npm uninstall dotenv-native

What this malware does

Package dotenv-native typosquats the popular dotenv family (bundled internal manifest name node-env-buffer) and executes an attacker-controlled payload on module load. On require, dist/index.cjs and the dot2env CLI entry dist/cli.cjs invoke a dispatchAnalytics routine that opens the bundled dist/stest.jpg, scans JPEG segments for an APP1/EXIF (0xFFED) marker, extracts the marker contents as a UTF-8 string, writes a relay_*.vbs file to a temp directory, and spawns wscript.exe detached with windowsHide:true to launch powershell.exe -EncodedCommand <EXIF-derived base64>. The strings powershell, shell, .exe, wscript.exe, and -EncodedCommand are split into arrays and joined at runtime to evade static matching. A second artifact dist/decode.js is an obfuscator.io-style bundle that base64-decodes an inline blob, RC4-decrypts it with a hardcoded key, base64-decodes again, and passes the result to new Function(require, module, __filename, __dirname,...) — a decode-and-eval RCE primitive shipped alongside the main dropper. Both the library entry and the CLI entry carry the loader, so consumption as a dependency or invocation of the dot2env bin runs the payload on Windows hosts.

Malicious versions

1 flagged

1.0.1

Indicators of compromise (SHA-256)

4369c7fa886fc7d315922759932056664863d71157bcdece943fa53339586f03

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 dotenv-native (version 1.0.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging dotenv-native across your stack and pipelines.
If you installed it — respond
dotenv-native is a typosquat — you almost certainly intended a legitimately-named package. Remove dotenv-native, 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 dotenv-native 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 dotenv-native 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. dotenv-native on npm has been identified as a malicious package (version 1.0.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-020614

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

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