Malicious Code Injection in mahesa-mieaceh38-riris: A Threat to npm Packages
Summary
MAL-2025-88154: Malicious code in mahesa-mieaceh38-riris (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
Background
The package 'mahesa-mieaceh38-riris' is part of a series of npm packages that emerged during the tea.xyz token reward campaign. These packages are designed to inflate developer reputation scores by automatically generating and publishing derivative packages with randomized names. The malicious nature of this package lies in its ability to modify critical files and republish variants, thereby polluting the npm registry.
Vulnerability Detail
The vulnerability in 'mahesa-mieaceh38-riris' originates from its inclusion in a campaign that floods the npm ecosystem with malicious packages. It contains scripts that alter the package.json file by removing private flags and changing version numbers. This allows the package to continuously republish itself and its variants, leading to potential security risks, including the exposure of sensitive data and the degradation of the npm registry's integrity.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall mahesa-mieaceh38-ririsIf 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 measure, you can restrict the installation of this package by using npm's package-lock.json to monitor dependencies. You can also use the following command to prevent the installation of any unwanted packages: 'npm install --no-optional'.
Conclusion
The 'mahesa-mieaceh38-riris' package poses a significant risk due to its malicious code designed to manipulate npm packages. It is crucial to remove this package and monitor your dependencies regularly to maintain the security of your projects.
See every vulnerability recorded for mahesa-mieaceh38-riris →
FAQ
The main threat is the modification of package.json files and the continuous republishing of malicious variants, which can compromise the integrity of the npm registry.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. By simply using your package-lock.json file, you can check for vulnerabilities without needing to install any software.
You should immediately uninstall the package using 'npm uninstall mahesa-mieaceh38-riris' and check for any other potentially malicious packages.
Regularly audit your dependencies and utilize tools like Vulert to monitor for vulnerabilities in real-time.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.
