ms-client-portal

ms-client-portal is a dependency-confusion package with no functional code; its README says the name is an internal project name exposed in the production web bundle of a health-sector client portal. Its preinstall and postinstall scripts each run a `node -e` one-liner on npm install that sends an HTTP GET to `http://38.242.235.206/depconf/ms-client-portal/preinstall` (and `/postinstall`) with the user name (`USER` or `USERNAME`), hostname and working directory in the query string. The npm account amahrou1a published versions 1.0.0 and 10.0.0 on 2026-10-31, and earlier the same day two more packages, internal-renderers and pandafortunerush, with the same beacon to the same server.

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

Source: amazon-inspector (67d0d267cb0260014f0950179e7b72b1ed9d05580577f0f68b03fb42ed930459)
The package's preinstall and postinstall lifecycle scripts in package.json run an inline `node -e` command that issues plain-HTTP GET requests to the bare IP 38.242.235.206 at the path /depconf/ms-client-portal/{pre,post}install, carrying the installer's USER/USERNAME environment variable, OS hostname (os.hostname()), and current working directory (process.cwd()) as query parameters. The requests fire automatically on `npm install` with no opt-in, no configurability, and no TLS. The destination is a bare-IP endpoint unrelated to any declared publisher, and the path structure (`/depconf/<package-name>/`) is the canonical shape of a dependency-confusion reconnaissance beacon used to identify internal environments that resolve a public package name instead of a private one.

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