Malicious Code Injection in xaver-ubi49-ruro Package

xaver-ubi49-ruro Updated 18 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-111099: Malicious code in xaver-ubi49-ruro (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 Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

The xaver-ubi49-ruro package is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to facilitate the automatic generation and publication of derivative packages, which can inflate developer reputation scores. However, it has been identified as containing malicious code that modifies package metadata and repackages itself under random names, leading to potential security risks.

Vulnerability Detail

The vulnerability in the xaver-ubi49-ruro package originates from its malicious intent to manipulate the npm registry. It includes scripts that remove private flags from package.json, alters version numbers, and generates random package names, which can lead to the pollution of the npm registry. This behavior not only compromises the integrity of the affected package but also poses a risk to developers who may unknowingly use these compromised packages in their projects.

How To Fix

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

npm uninstall xaver-ubi49-ruro

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 workaround, you can manually remove the xaver-ubi49-ruro package from your project by running the following command: npm uninstall xaver-ubi49-ruro. Additionally, consider using alternative packages that do not exhibit malicious behavior.

Conclusion

The xaver-ubi49-ruro package has been identified as containing malicious code that can compromise the integrity of npm packages. It is essential to remove this package from your project and monitor for any vulnerabilities using tools like Vulert. Staying informed and proactive can help protect your applications from such threats.

See every vulnerability recorded for xaver-ubi49-ruro →

Share this vulnerability

FAQ

The xaver-ubi49-ruro package is an npm package associated with the tea.xyz token reward campaign, designed to generate and publish derivative packages.

The malicious code can compromise your project's integrity by modifying package metadata and introducing potentially harmful packages into the npm registry.

If you have installed the xaver-ubi49-ruro package, it is crucial to uninstall it immediately and monitor your project for any unusual behavior.

Yes, tools like Vulert can monitor your project for open-source vulnerabilities in real-time using just the package-lock.json file.

You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.

How To Fix

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

npm uninstall xaver-ubi49-ruro

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