Malicious Code Injection in mahesa-oncom68-ruro Package

mahesa-oncom68-ruro Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-105483: Malicious code in mahesa-oncom68-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-oncom68-ruro package is part of the npm ecosystem, often utilized in various JavaScript applications. This package has been identified as part of a larger campaign that aims to exploit npm by flooding the registry with malicious packages. Its primary functionality is to serve as a token reward mechanism for the tea.xyz protocol, but it has been compromised to include harmful scripts.

Vulnerability Detail

The vulnerability in the mahesa-oncom68-ruro package stems from its inclusion in a malicious campaign that generates and publishes derivative packages with randomized names. These packages contain scripts that modify the package.json file to remove private flags, alter version numbers, and continuously republish variants, thereby polluting the npm registry. The origin of this issue is linked to the tea.xyz token reward campaign, which incentivizes the creation of such malicious packages. The ramifications include potential security risks for developers who unknowingly use these packages, as they may inadvertently expose their applications to further vulnerabilities.

How To Fix

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

npm uninstall mahesa-oncom68-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-oncom68-ruro package altogether and look for alternative packages that provide similar functionality without the associated risks.

Conclusion

The mahesa-oncom68-ruro package has been compromised as part of a malicious campaign that affects the npm ecosystem. It is crucial for developers to remove this package from their projects and monitor for vulnerabilities to ensure the security of their applications.

See every vulnerability recorded for mahesa-oncom68-ruro →

Share this vulnerability

FAQ

The mahesa-oncom68-ruro package is an npm package that has been identified as part of a malicious campaign to exploit the npm registry.

If your application uses the mahesa-oncom68-ruro package, it may be exposed to security risks, including the potential for malicious code execution.

You should remove the mahesa-oncom68-ruro package from your project and check for any alternative packages that are secure.

Yes, you can use Vulert, which monitors and alerts in real-time for open-source vulnerabilities in your software by analyzing your 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 mahesa-oncom68-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