ms-client-portal (npm) · Malicious Code
Affects ms-client-portalSource GCVE Database
Malicious package : remove ms-client-portal and rotate any secrets on hosts that installed it.
Data as of 2 Nov 2026, 19:44 UTC
Malicious package
Published to npm · OSV MAL-2026-18449
What to do
Remove ms-client-portal from every project, lockfile and image that pulls it in. Treat any host that installed it as compromised: rotate the credentials, tokens and keys it could read, from a clean machine.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| npmms-client-portal | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
Description
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: 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.