Malicious Code Injection in budi-ubi80-ruro: A Threat to npm Ecosystem

budi-ubi80-ruro Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-100181: Malicious code in budi-ubi80-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 package budi-ubi80-ruro is part of the npm ecosystem, which is a popular package manager for JavaScript. It is often used to share and manage code libraries. However, this particular package has been identified as part of a malicious campaign that aims to exploit the npm registry by flooding it with derivative packages. These packages are designed to inflate developer reputation scores through automated publishing scripts.

Vulnerability Detail

The vulnerability in budi-ubi80-ruro stems from its malicious code that modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior is part of a broader scheme to pollute the npm registry by continuously republishing variants of the package. The origin of this vulnerability is linked to the tea.xyz token reward campaign, which has been associated with numerous malicious packages targeting npm users. The ramifications include potential security risks for developers who inadvertently use these packages, as they may unknowingly contribute to the pollution of the npm ecosystem.

How To Fix

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

npm uninstall budi-ubi80-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 temporary workaround, you can avoid using the budi-ubi80-ruro package and instead look for alternative packages that provide similar functionality without the associated risks. Always verify the integrity and reputation of packages before including them in your project.

Conclusion

The budi-ubi80-ruro package poses a significant threat to the npm ecosystem due to its malicious behavior aimed at manipulating the npm registry. It is crucial for developers to remain vigilant, regularly audit their dependencies, and utilize tools like Vulert to monitor for vulnerabilities. By taking proactive measures, developers can safeguard their projects from potential risks associated with malicious packages.

See every vulnerability recorded for budi-ubi80-ruro →

Share this vulnerability

FAQ

budi-ubi80-ruro is an npm package that has been identified as malicious, part of a campaign to flood the npm registry with derivative packages.

Using the budi-ubi80-ruro package can lead to security risks, including the potential for your project to be associated with malicious activities and the pollution of the npm registry.

You can use Vulert, which monitors open-source vulnerabilities in real-time. By checking your package-lock.json file, you can identify if your application is affected by this vulnerability.

If you have used the budi-ubi80-ruro package, you should uninstall it immediately and look for alternative packages. Ensure to check your project for any other potentially malicious dependencies.

To prevent future vulnerabilities, regularly audit your dependencies, use tools like Vulert for real-time monitoring, and only install packages from trusted sources.

How To Fix

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

npm uninstall budi-ubi80-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