Malicious Code Detected in com.microsoft.azure.remote-rendering Package

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-17323: Malicious code in com.microsoft.azure.remote-rendering (npm). Affected versions are not published. 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 com.microsoft.azure.remote-rendering package is an npm library designed to facilitate remote rendering capabilities in applications using Microsoft Azure. It allows developers to leverage cloud-based rendering services to enhance the visual quality of their applications. However, this package has been found to contain malicious code, posing significant security risks to users and their applications.

Vulnerability Detail

The vulnerability in the com.microsoft.azure.remote-rendering package stems from the inclusion of malicious code that can compromise the integrity and security of applications using this library. This malicious code can lead to unauthorized access, data breaches, and potential exploitation of the affected systems. The issue was introduced in version 0 and has been documented as MAL-2025-17323, highlighting the urgent need for users to address this vulnerability.

How To Fix

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

npm uninstall com.microsoft.azure.remote-rendering

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 workaround, users can remove the com.microsoft.azure.remote-rendering package from their project until a secure version is released. This can be done using the command: npm uninstall com.microsoft.azure.remote-rendering. Additionally, consider using alternative packages that provide similar functionality without the associated risks.

Conclusion

The discovery of malicious code in the com.microsoft.azure.remote-rendering package poses a significant threat to applications utilizing this library. Users are strongly encouraged to take immediate action by updating or removing the package to safeguard their applications. Utilizing tools like Vulert can help in monitoring for such vulnerabilities in the future.

See every vulnerability recorded for com.microsoft.azure.remote-rendering →

Share this vulnerability

FAQ

The malicious code can lead to unauthorized access and data breaches, compromising the security of applications that utilize the package.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. By utilizing the Vulert playground, you can check if your application is affected without requiring any installation.

Currently, there is no safe version of the com.microsoft.azure.remote-rendering package available. Users are advised to uninstall the package until a secure version is released.

If immediate updates are not possible, consider removing the package and using alternative libraries that provide similar functionality without the associated risks.

Regularly check for updates from the package maintainers and utilize tools like Vulert to monitor your dependencies for any new vulnerabilities.

How To Fix

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

npm uninstall com.microsoft.azure.remote-rendering

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