Malicious Code Detected in vscode-azure-mcp-server: A Critical Security Alert

vscode-azure-mcp-server Updated 16 Dec 2025

Summary

16/12/2025
CRITICAL
No i
Critical
Not published

MAL-2025-192601: Malicious code in vscode-azure-mcp-server (npm). Affects vscode-azure-mcp-server versions 1.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 Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

vscode-azure-mcp-server is an npm package designed to facilitate interactions with Azure services. It is commonly used in development environments to manage Azure resources efficiently. However, the package version 1.0.0 has been flagged for containing malicious code that compromises user security by communicating with a domain linked to malicious activities.

Vulnerability Detail

The vulnerability in vscode-azure-mcp-server arises from its communication with a domain associated with malicious activities. This behavior poses significant risks, including unauthorized data access, potential data breaches, and exploitation of the user's environment. The malicious nature of the package was identified by the OpenSSF Package Analysis project, which highlights the importance of scrutinizing third-party packages for security threats.

How To Fix

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

npm uninstall vscode-azure-mcp-server

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

As a temporary measure, users can avoid using the vscode-azure-mcp-server package altogether until a secure version is released. Additionally, consider using alternative packages that provide similar functionality without the associated risks.

Conclusion

The discovery of malicious code in the vscode-azure-mcp-server package underscores the importance of vigilance when using third-party libraries. Users are advised to uninstall the affected package and monitor for updates. Utilizing tools like Vulert can help maintain the security of your applications.

See every vulnerability recorded for vscode-azure-mcp-server →

Share this vulnerability

FAQ

The main issue is that the package communicates with a domain linked to malicious activities, posing security risks.

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

Currently, there is no patched version available. Users should uninstall the affected version until a secure update is released.

If you have installed vscode-azure-mcp-server, you should uninstall it immediately using the command npm uninstall vscode-azure-mcp-server.

Regularly monitor your dependencies using tools like Vulert and keep your packages updated to the latest secure versions.

How To Fix

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

npm uninstall vscode-azure-mcp-server

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