Malicious Code Injection in mahesa-getuk5-ruro Package: A Threat to npm Users

mahesa-getuk5-ruro Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-105467: Malicious code in mahesa-getuk5-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 Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The mahesa-getuk5-ruro package is part of the npm ecosystem, primarily used for JavaScript applications. It is associated with the tea.xyz token reward campaign, which has been known to flood the npm registry with numerous packages. This package, like others in the campaign, is designed to manipulate npm's publishing system, potentially leading to reputation inflation for malicious actors.

Vulnerability Detail

The vulnerability in the mahesa-getuk5-ruro package stems from its inclusion in a malicious campaign that employs autopublish scripts to generate and publish derivative packages with randomized names. This behavior modifies the package.json file by removing private flags and altering version numbers, which can lead to the pollution of the npm registry. The ramifications include the potential for developers to unknowingly install compromised packages, leading to security risks in their applications.

How To Fix

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

npm uninstall mahesa-getuk5-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-getuk5-ruro package until a secure version is released. Additionally, consider using npm audit to identify and address vulnerabilities in your project dependencies.

Conclusion

The mahesa-getuk5-ruro package poses a significant risk due to its malicious code that alters package metadata and floods the npm registry. It is crucial for developers to stay vigilant, update their dependencies, and utilize tools like Vulert to monitor for vulnerabilities.

See every vulnerability recorded for mahesa-getuk5-ruro →

Share this vulnerability

FAQ

The mahesa-getuk5-ruro package is an npm package associated with the tea.xyz token reward campaign, which has been linked to malicious activities in the npm ecosystem.

This vulnerability can lead to the installation of compromised packages, which may introduce security risks and affect the integrity of your application.

If you have installed the mahesa-getuk5-ruro package, you should immediately update it to the latest version or remove it from your project.

You can use tools like Vulert, which monitors your package-lock.json file for open-source 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 needing to sign up.

How To Fix

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

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