Malicious Code Injection in hendra-rangginang95-ruro Package
Summary
MAL-2025-103691: Malicious code in hendra-rangginang95-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
Background
The hendra-rangginang95-ruro package is part of the npm ecosystem, often used for JavaScript development. This package has been identified as part of a malicious campaign that floods the npm registry with derivative packages. Its primary function is to automate the generation and publication of these packages, which can lead to reputation inflation for developers involved in the tea.xyz token reward campaign.
Vulnerability Detail
The vulnerability stems from the presence of malicious code within the hendra-rangginang95-ruro package. This code modifies the package.json file to remove private flags, alters version numbers, and generates random package names, thereby polluting the npm registry. The malicious payload is designed to automatically publish these variants, which can compromise the integrity of the npm ecosystem and potentially lead to security risks for developers and users relying on these packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall hendra-rangginang95-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 workaround, you can manually remove the hendra-rangginang95-ruro package from your project by executing the following command: npm uninstall hendra-rangginang95-ruro. Additionally, consider using tools like Vulert to monitor your package-lock.json for any vulnerabilities in real-time.
Conclusion
The hendra-rangginang95-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 remove this package and utilize monitoring tools like Vulert to safeguard their projects against potential vulnerabilities.
See every vulnerability recorded for hendra-rangginang95-ruro →
FAQ
It is an npm package that has been identified as part of a malicious campaign to inflate developer reputation scores through automated package publishing.
The vulnerability can lead to the pollution of the npm registry and may introduce security risks if your project relies on compromised packages.
You should uninstall the hendra-rangginang95-ruro package immediately and monitor for any updates or patches from the npm registry.
Yes, Vulert allows you to monitor your package-lock.json for vulnerabilities in real-time without requiring code access or installation.
Regularly audit your dependencies, use tools like Vulert for monitoring, and stay informed about known vulnerabilities in the npm ecosystem.