Critical Vulnerability in com.google.xr.xdtk: Malicious Code Detected

com.google.xr.xdtk Updated 02 Oct 2025

Summary

31/07/2025
CRITICAL
No i
Critical
Not published

MAL-2025-6407: Malicious code in com.google.xr.xdtk (npm). Affects com.google.xr.xdtk versions 1.1.1. 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 MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

The package 'com.google.xr.xdtk' is an npm package designed for extended reality development, providing tools and resources for developers to create immersive experiences. However, it has been identified with a serious vulnerability that allows malicious code execution, potentially compromising user systems and data integrity.

Vulnerability Detail

The vulnerability identified as MAL-2025-6407 originates from malicious code embedded within version 1.1.1 of the package. This code can lead to unauthorized access, data theft, or system compromise. The issue was discovered by ReversingLabs, highlighting the importance of scrutinizing third-party packages for hidden threats.

How To Fix

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

npm uninstall com.google.xr.xdtk

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, you can remove the affected package from your project until a secure version is released. Use the following command to uninstall: 'npm uninstall com.google.xr.xdtk'. This will prevent any potential exploitation while you await a fix.

Conclusion

The discovery of the MAL-2025-6407 vulnerability in the com.google.xr.xdtk package underscores the critical need for vigilance when using third-party libraries. Users are encouraged to update their packages promptly and utilize tools like Vulert to monitor for vulnerabilities in real-time.

See every vulnerability recorded for com.google.xr.xdtk →

Share this vulnerability

FAQ

The vulnerability involves malicious code that can compromise user systems and data integrity.

You can use Vulert's playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.

If an immediate update is not possible, consider uninstalling the package to mitigate risks until a secure version is available.

The vulnerability was discovered by ReversingLabs, a cybersecurity firm specializing in threat detection.

Check the package repository for a patched version. If available, update the package using 'npm update com.google.xr.xdtk'.

How To Fix

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

npm uninstall com.google.xr.xdtk

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