NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
Malicious package

env-localnpm

Advisory published Updated

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
  1. Find it

    Search your lockfiles and build artifacts for env-local (2 malicious versions).

  2. 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.

  3. Did it already run?

    If env-local 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. 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.

Explore

env-local (npm) malicious package — MAL-2026-13694 | O3 Security