Malicious Code Injection in mahesa-ubi79-ruro Package

mahesa-ubi79-ruro Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-105507: Malicious code in mahesa-ubi79-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 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 mahesa-ubi79-ruro package is part of the npm ecosystem, which is widely used for JavaScript package management. This package has been identified as part of a malicious campaign that floods the npm registry with derivative packages aimed at inflating developer reputation scores for token rewards. The package's functionality is compromised by the inclusion of scripts that manipulate its metadata and continuously republish variants, leading to pollution of the npm registry.

Vulnerability Detail

The vulnerability originates from the mahesa-ubi79-ruro package being part of a malicious campaign that includes scripts designed to modify the package.json file. These scripts remove private flags, alter version numbers, and generate random package names, which can lead to significant issues such as reputation damage for developers, potential security risks for applications using these packages, and an overall polluted npm registry. The malicious payload is designed to operate autonomously, continuously republishing variants that can confuse developers and users alike.

How To Fix

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

npm uninstall mahesa-ubi79-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 mahesa-ubi79-ruro package and replace it with a trusted alternative. Regularly monitor your dependencies and consider using tools like Vulert to check for vulnerabilities in your package-lock.json file.

Conclusion

The mahesa-ubi79-ruro package has been identified as a malicious entity within the npm ecosystem, posing significant risks to developers and their applications. It is crucial to remove this package and monitor your dependencies for vulnerabilities to maintain the integrity and security of your projects.

See every vulnerability recorded for mahesa-ubi79-ruro →

Share this vulnerability

FAQ

The mahesa-ubi79-ruro package is an npm package that has been identified as part of a malicious campaign to inflate developer reputation scores.

The vulnerability can lead to the inclusion of malicious code in your application, potentially compromising security and damaging your reputation as a developer.

You should uninstall the mahesa-ubi79-ruro package immediately and check your application for any potential impacts.

You can use tools like Vulert, which monitors your package-lock.json file for vulnerabilities in real-time without requiring code access or installation.

Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.

How To Fix

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

npm uninstall mahesa-ubi79-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