Which versions of env-local are malicious?

The following npm versions of env-local are flagged malicious: 18.4.2, 18.4.3. Treat any of these as compromised.

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

Remove env-local 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 env-local — how do I know if it already compromised me?

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

Yes — env-local is associated with the IN-MAL-2026-017231, IN-MAL-2026-017355 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-local 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-local (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-local across your stack and pipelines.

Malicious package

env-localnpm

env-local is a confirmed malicious npm package (MAL-2026-13694) that executes malicious code on install (malicious versions 18.4.2, 18.4.3). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in env-local (npm)

MAL-2026-13694

Immediate action

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

npm uninstall env-local

What this malware does

env-local presents itself as a dotenv-compatible.env loader (README, keywords, and API mirror motdotla/dotenv), but lib/main.js unconditionally requires lib/tui-options.js, which activates a full-host spyware payload on module load. tui-options.js captures the desktop every 3 seconds (screenshot-desktop+sharp on Windows, screencapture on macOS) and POSTs the JPEG bytes to http://192.99.204.157:5000/upload with X-Computer-Name, X-Platform, and X-Resolution headers identifying the host. In parallel, a 1-second interval polls http://192.99.204.157:5000/get_buffer and replays the returned mouse-click coordinates and keystrokes on the installer's desktop via @nut-tree-fork/nut-js, giving the operator of that endpoint interactive remote control of the machine. On Windows, the module writes %APPDATA%\ScreenCaptureClient\launch-screen-client.vbs and registers HKCU\Software\Microsoft\Windows\CurrentVersion\Run\ScreenCaptureClient via reg.exe to invoke the launcher with wscript.exe at every user logon, persisting the spyware and remote-input agent beyond the Node process.

Malicious versions

2 flagged

18.4.218.4.3

Indicators of compromise (SHA-256)

ac368f7cba943b89781656da7f45ac393cf8b105eaa54a29c42a78622a2fde0b

7faefbcd9110b5e08b469d72d6541875ba4e2702c4490d1a24c37b313160f86b

Detection & response playbook

Malicious package

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for env-local (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-local across your stack and pipelines.
If you installed it — respond
Remove env-local 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 env-local 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-local 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-local on npm has been identified as a malicious package (versions 18.4.2, 18.4.3 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-017231IN-MAL-2026-017355

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks env-local-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