Malicious code in ms-client-portal (npm)

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

not scored

EPSS

No dated EPSS signal available.

As published by the source; long descriptions are shortened.

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…

Published by the source

31 Oct 2026, 13:10 UTC

Last modified by the source

2 Nov 2026, 18:30 UTC

Source last checked

3 Nov 2026, 06:00 UTC

1. Revision 2 · amended · 3 Nov 2026

   Amended from osv record MAL-2026-18449

2. Revision 1 · created · 2 Nov 2026

   Published from osv record MAL-2026-18449

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: GHSA-q7rp-q644-j8rp

Advisory: Malicious code in ms-client-portal (npm)
IDs: GHSA-q7rp-q644-j8rp
Record: https://patchnext.com/advisories/mal-2026-18449 (revision 2, source checked 3 Nov 2026, 06:00 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Unrated
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor response not established. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm ms-client-portal: affected every version

## Suggested inspection (read-only)
- `npm ls ms-client-portal --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## Supported action
No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on ms-client-portal.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/MAL-2026-18449 (OSV record MAL-2026-18449 lists affected ranges: npm ms-client-portal >=1.0.0 =10.0.0 <=10.0.0)
- Verified: https://osv.dev/vulnerability/MAL-2026-18449 (OSV record MAL-2026-18449 lists affected ranges: npm ms-client-portal >=0)

Commands are suggestions: review each one before running it.