Malicious Code Injection in erwin-kemplang71-ruro Package
Summary
MAL-2025-102205: Malicious code in erwin-kemplang71-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 erwin-kemplang71-ruro package 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 floods the npm registry with harmful packages. Its primary function is to generate and publish derivative packages with randomized names, which can inflate developer reputation scores for token rewards in the tea.xyz protocol.
Vulnerability Detail
The vulnerability stems from the package's malicious payload, which modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior leads to the continuous republishing of variants, polluting the npm registry and potentially compromising the integrity of dependent projects. The origin of this vulnerability is linked to a campaign aimed at exploiting npm's publishing mechanisms for malicious gain.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall erwin-kemplang71-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 prevent the installation of this package by using npm's package-lock.json file to lock your dependencies. Additionally, consider using tools like Vulert to monitor your project for vulnerabilities. You can check if your application is affected by this vulnerability using the Vulert playground at https://vulert.com/scanner without any signup.
Conclusion
The erwin-kemplang71-ruro package poses a significant risk due to its malicious behavior aimed at exploiting the npm registry. It is crucial for developers to remove this package and utilize monitoring tools like Vulert to safeguard their projects from potential vulnerabilities.
See every vulnerability recorded for erwin-kemplang71-ruro →
FAQ
It is an npm package that has been identified as part of a malicious campaign to inflate developer reputation scores through the generation of harmful derivative packages.
The vulnerability can lead to the pollution of the npm registry and may compromise the integrity of your project by introducing malicious code.
You should uninstall the package immediately and monitor your project for any further vulnerabilities using tools like Vulert.
Currently, there is no patch for the erwin-kemplang71-ruro package. The best course of action is to remove it from your project.
You can use Vulert, which monitors your package-lock.json file to alert you in real-time for open-source vulnerabilities.
