---
id: "MAL-2026-18449"
kind: "package"
aliases: ["MAL-2026-18449"]
title: "Malicious code in ms-client-portal (npm)"
severity: "critical"
cvss: null
epss: null
exploited: false
status: "open"
category: "package"
products: [{"name": "ms-client-portal", "fixed": [], "affected": "= 1.0.0; = 10.0.0", "ecosystem": "npm"}]
ecosystems: ["npm"]
tags: ["malicious", "package"]
not_affected_if: []
published_at: "2026-10-31T13:10:23+00:00"
first_seen_at: "2026-11-02T06:51:32+00:00"
updated_at: "2026-11-02T06:53:35+00:00"
sources: [{"source": "osv-malicious", "url": "https://osv.dev/vulnerability/MAL-2026-18449", "first_seen_at": "2026-11-02T06:51:32+00:00"}]
---

# Malicious code in ms-client-portal (npm)

## Affected

- npm:ms-client-portal affected = 1.0.0; = 10.0.0 fixed ?

## Timeline

- 2026-11-02T06:51:32+00:00 osv-malicious https://osv.dev/vulnerability/MAL-2026-18449

## From the sources

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.

---

_Free to read at a human pace. An API with keys and an MCP server are in preparation; early access: hello@infrastack.ai_