Malicious Code Injection in erwin-rangi41-ruro: A Threat to npm Packages
Summary
MAL-2025-102223: Malicious code in erwin-rangi41-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 package 'erwin-rangi41-ruro' is part of the npm ecosystem, which is widely used for JavaScript package management. This package has been identified as part of a malicious campaign that aims to exploit the npm registry by flooding it with derivative packages. These packages often contain scripts designed to manipulate package metadata and inflate developer reputation scores for token rewards.
Vulnerability Detail
The vulnerability in 'erwin-rangi41-ruro' originates from its association with the tea.xyz token reward campaign. The malicious code embedded in this package modifies the package.json file by removing private flags, altering version numbers, and generating random package names. This behavior leads to the continuous republishing of these variants, which pollutes the npm registry and can potentially compromise the integrity of other packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall erwin-rangi41-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 measure, you can avoid using the 'erwin-rangi41-ruro' package and replace it with a trusted alternative. Regularly audit your dependencies using tools like npm audit to identify and mitigate vulnerabilities.
Conclusion
The 'erwin-rangi41-ruro' package poses a significant threat due to its malicious code designed to manipulate npm registry data. It is essential to remove this package from your projects and stay vigilant about your dependencies to maintain the security of your applications.
See every vulnerability recorded for erwin-rangi41-ruro →
FAQ
The malicious code can lead to the pollution of the npm registry, potentially affecting the integrity and security of other packages.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check your application without any signup.
Immediately uninstall the package using 'npm uninstall erwin-rangi41-ruro' and review your dependencies for any other malicious packages.
Yes, consider using well-established and trusted packages that serve the same purpose without the associated risks.
Regularly audit your dependencies, keep your packages updated, and utilize tools like Vulert to monitor for vulnerabilities.
