Advisory

MAL-2026-17681

Also known as: GHSA-fw57-xw67-r253

Malicious package Its source marks this package as malicious: it is not a vulnerability in a legitimate one.

Summary

Malicious code in node-env-resolve (npm)

Details

---
_-= Per source details. Do not edit below this line.=-_

Source: amazon-inspector (6f3e0e1b364a3d74534d6ce1eca74778a85e508cf10952f84f36bf1badd8a581)
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.

Source: ghsa-malware (1c4c431ade8f90043103688562db8f180939f4d83dc642ea4682d4de7766d4dd)
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.

Severity

Not rated by the source.

Dates

Published
2026-10-08 14:26 UTC
Modified
2026-10-08 15:45 UTC

Affected packages and fixes

node-env-resolve

npm · All systems

Affected

  • introduced 0 (semver)

Fixed versions

None listed

Fix

No fixed version is listed.

Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.

Check your own computer: guard packages check

View this record on OSV.dev

Source

Source: OpenSSF Malicious Packages · Apache-2.0

Sources & licences