Critical Malicious Code Vulnerability in com.microsoft.mixedreality.input Package

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-17328: Malicious code in com.microsoft.mixedreality.input (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 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

The com.microsoft.mixedreality.input package is designed for handling input from mixed reality devices, providing developers with tools to create immersive experiences. It is widely used in applications that leverage Microsoft's mixed reality technologies. However, this package has been found to contain malicious code, posing significant risks to applications that depend on it.

Vulnerability Detail

The vulnerability originates from the presence of malicious code within the com.microsoft.mixedreality.input package. This malicious code can compromise the security of applications utilizing this package, potentially leading to unauthorized access, data breaches, or other malicious activities. The issue is particularly concerning as it affects all versions of the package starting from its introduction, making it imperative for users to take immediate action.

How To Fix

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

npm uninstall com.microsoft.mixedreality.input

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, you can remove the package from your project by executing the following command: npm uninstall com.microsoft.mixedreality.input. This will help mitigate the risk until a secure version is released.

Conclusion

The discovery of malicious code in the com.microsoft.mixedreality.input package poses a serious threat to applications using it. Immediate action is required to mitigate risks, including updating or uninstalling the package. Users are encouraged to stay vigilant and utilize tools like Vulert for real-time monitoring of vulnerabilities.

See every vulnerability recorded for com.microsoft.mixedreality.input →

Share this vulnerability

FAQ

The malicious code can lead to unauthorized access and potential data breaches in applications that utilize this package.

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

If an update is not possible, it is recommended to uninstall the package until a secure version is released.

Currently, there is no safe version of the com.microsoft.mixedreality.input package available due to the vulnerability affecting all versions.

You can monitor the official repository of the package or subscribe to security advisories related to npm packages for updates.

How To Fix

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

npm uninstall com.microsoft.mixedreality.input

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