Which versions of ms-client-portal are malicious?

The following npm versions of ms-client-portal are flagged malicious: 1.0.0, 10.0.0. Treat any of these as compromised.

How do I remediate ms-client-portal if I installed it?

ms-client-portal establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.

I already installed ms-client-portal — how do I know if it already compromised me?

If ms-client-portal was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Is ms-client-portal part of a known attack campaign?

Yes — ms-client-portal is associated with the GHSA-q7rp-q644-j8rp campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find ms-client-portal across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for ms-client-portal (2 malicious versions).

Malicious package

ms-client-portalnpm

Advisory published Oct 31, 2026Updated Nov 2, 2026

ms-client-portal is a confirmed malicious npm package (MAL-2026-18449) that opens a backdoor for remote access (malicious versions 1.0.0, 10.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in ms-client-portal (npm)

MAL-2026-18449

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall ms-client-portal

What this malware does

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.

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.

Malicious versions

2 flagged

1.0.010.0.0

Indicators of compromise (SHA-256)

e3e8e42f6545a90f07acd9d7f519f879050f778687a1bec78b0391981adb1b87

Detection & response playbook

Backdoor / remote access

Find it
Search your lockfiles and build artifacts for ms-client-portal (2 malicious versions).
If you installed it — respond
ms-client-portal establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.
Did it already run?
If ms-client-portal was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. ms-client-portal on npm has been identified as a malicious package (versions 1.0.0, 10.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-q7rp-q644-j8rp

References

Credits

InvisiRisk, Inc. · finder

Detect & block this

O3 blocks ms-client-portal-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the C2 callback and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database