Malicious Code Injection in mahesa-getuk18-ruro: A Threat to npm Ecosystem
Summary
MAL-2025-105466: Malicious code in mahesa-getuk18-ruro (npm). Affected versions are not published. No fix is published. How to fix ↓
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.
No signup required · Results in about 60 seconds
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
Background
The package 'mahesa-getuk18-ruro' is part of the npm ecosystem and appears to be associated with the tea.xyz token reward campaign. This package is designed to manipulate the npm registry by generating and publishing derivative packages with randomized names, which can inflate developer reputation scores for token rewards. Its functionality is compromised due to the presence of malicious scripts that alter package metadata.
Vulnerability Detail
The vulnerability in 'mahesa-getuk18-ruro' originates from its association with malicious code that modifies the package.json file. This code removes private flags, alters version numbers, and creates random package names, leading to the continuous republishing of variants that pollute the npm registry. The ramifications include potential security risks for developers and users who may unknowingly install these compromised packages, leading to further exploitation.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall mahesa-getuk18-ruroIf 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, consider removing the 'mahesa-getuk18-ruro' package from your project until a secure version is available. You can do this by executing the command: 'npm uninstall mahesa-getuk18-ruro'. Additionally, monitor your package-lock.json file for any unauthorized changes.
Conclusion
The 'mahesa-getuk18-ruro' package poses a significant risk due to its malicious code that alters package metadata and pollutes the npm registry. It is crucial for developers to stay vigilant, update their dependencies, and utilize tools like Vulert to monitor for vulnerabilities in real-time.
See every vulnerability recorded for mahesa-getuk18-ruro →
FAQ
The primary risk is the potential for malicious code to alter your project's dependencies and metadata, leading to security vulnerabilities.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software. Visit Vulert Scanner to check your application without any signup.
If you have installed 'mahesa-getuk18-ruro', it is recommended to uninstall it immediately and monitor your project for any unauthorized changes.
Currently, there is no specific patched version available for 'mahesa-getuk18-ruro'. Regularly check the package repository for updates.
To prevent similar vulnerabilities, regularly audit your dependencies, use tools like Vulert for monitoring, and avoid installing packages from unverified sources.
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
