Which versions of node-env-resolve are malicious?

The following npm versions of node-env-resolve are flagged malicious: 1.2.3. Treat any of these as compromised.

How do I remediate node-env-resolve if I installed it?

node-env-resolve establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.

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

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

Yes — node-env-resolve is associated with the IN-MAL-2026-021211, GHSA-fw57-xw67-r253 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 node-env-resolve across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for node-env-resolve (version 1.2.3).

Malicious package

node-env-resolvenpm

Advisory published Oct 8, 2026Updated Oct 8, 2026

node-env-resolve is a confirmed malicious npm package (MAL-2026-17681) that opens a backdoor for remote access (malicious version 1.2.3). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in node-env-resolve (npm)

MAL-2026-17681

Immediate action

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

npm uninstall node-env-resolve

What this malware does

The package is advertised as an environment configuration resolver but its postinstall script installs a hidden persistent agent into user-level directories named to resemble Node tooling (~/.node-gyp-cache, %APPDATA%\node-gyp-cache, /opt/connector-service) and registers autostart via the Windows Registry Run key (node-gyp-cache), a macOS LaunchAgent (com.user.connector), or a Linux autostart desktop entry, then spawns the agent detached. The agent entrypoint registers the host with the hardcoded C2 at https://connector-server-xi.vercel.app, polls /api/agent/signal/poll?machineId=, and opens a WebRTC peer session whose inbound commands are dispatched to mouse and keyboard input synthesis, screen capture (JPEG frames over the data channel), microphone capture (PCM audio), and arbitrary filesystem operations (listDirectory, readFileContent, readFileBinary base64 up to 10MB, zipFolder up to 50MB, deleteItem, saveUploadedFile) rooted under the user's home directory. A dedicated browserHistory.js copies Chrome, Edge, and Firefox history SQLite databases (including -wal) to temp and returns URLs, titles, visit counts, and timestamps back over the P2P meta channel on history:request. Internal names (Windows System Connector, System connectivity and update service, com.user.connector, node-gyp-cache) are chosen to blend into legitimate OS/Node tooling and hide the agent from autostart inspection.

Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

Malicious versions

1 flagged

1.2.3

Indicators of compromise (SHA-256)

6f3e0e1b364a3d74534d6ce1eca74778a85e508cf10952f84f36bf1badd8a581

1c4c431ade8f90043103688562db8f180939f4d83dc642ea4682d4de7766d4dd

Detection & response playbook

Backdoor / remote access

Find it
Search your lockfiles and build artifacts for node-env-resolve (version 1.2.3).
If you installed it — respond
node-env-resolve establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.
Did it already run?
If node-env-resolve 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. node-env-resolve on npm has been identified as a malicious package (version 1.2.3 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-021211GHSA-fw57-xw67-r253

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks node-env-resolve-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the C2 callback and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database