Malicious Code Detected in Microsoft CMS Client: npm Package Vulnerability

microsoft-cms-client Updated 21 Feb 2026

Summary

21/02/2026
CRITICAL
No i
Critical
Not published

MAL-2026-978: Malicious code in microsoft-cms-client (npm). Affects microsoft-cms-client versions 99.0.0. No fix is published. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The 'microsoft-cms-client' package is a Node.js library designed for managing content in Microsoft CMS environments. It is widely used for its ease of integration and functionality in web applications. However, version 99.0.0 has been flagged for malicious activity, raising concerns about its security and integrity.

Vulnerability Detail

The vulnerability in the 'microsoft-cms-client' package arises from its communication with a domain associated with malicious activities. This could potentially lead to data breaches, unauthorized access, or other security incidents. The OpenSSF Package Analysis project identified this issue, emphasizing the need for immediate attention from users of this package.

How To Fix

This package is malicious. Remove it and rotate any credentials it could have accessed.

npm uninstall microsoft-cms-client

If it arrived as a transitive dependency, remove the package that pulled it in, then reinstall.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Workaround

If immediate updating is not feasible, consider removing the package from your project or replacing it with an alternative library that offers similar functionality without the associated risks.

Conclusion

The 'microsoft-cms-client' package version 99.0.0 has been identified as malicious due to its communication with harmful domains. Users are urged to update or remove the package to mitigate potential risks. Tools like Vulert can assist in monitoring for such vulnerabilities in real-time.

See every vulnerability recorded for microsoft-cms-client →

Share this vulnerability

FAQ

It is a Node.js library used for managing content in Microsoft CMS environments, facilitating integration and functionality in web applications.

A malicious package is one that engages in harmful activities, such as communicating with harmful domains or compromising user data.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check your application without needing to sign up.

Consider removing the package or replacing it with a safer alternative until you can update to a patched version.

Utilize tools like Vulert that provide real-time monitoring and alerts for open-source vulnerabilities in your software.

How To Fix

This package is malicious. Remove it and rotate any credentials it could have accessed.

npm uninstall microsoft-cms-client

If it arrived as a transitive dependency, remove the package that pulled it in, then reinstall.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback