Malicious Code Injection in erwin-kentang35-ruro: A Threat to npm Users
Summary
MAL-2025-102206: Malicious code in erwin-kentang35-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-kentang35-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. It is designed to generate and publish derivative packages with altered metadata, potentially affecting developers' reputations and polluting the npm registry.
Vulnerability Detail
The vulnerability originates from a malicious payload embedded within the erwin-kentang35-ruro package. This payload modifies the package.json file to remove private flags, alters version numbers, and generates random package names, primarily themed around Indonesian culture. The malicious scripts (auto.js, autopublish.js, etc.) continuously republish these variants, leading to an inflated developer reputation score for the perpetrators and cluttering the npm registry with unwanted packages. This poses significant risks, including the potential for developers to inadvertently use compromised packages, leading to security breaches in their applications.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall erwin-kentang35-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-kentang35-ruro package and monitor your project's dependencies for any signs of malicious activity. You can also use tools like Vulert to scan your package-lock.json file for vulnerabilities. Here’s how you can use Vulert: Visit https://vulert.com/scanner and upload your package-lock.json file to check for any vulnerabilities without needing to sign up.
Conclusion
The erwin-kentang35-ruro package poses a significant threat to npm users due to its embedded malicious code. It is essential to remove this package from your projects and utilize tools like Vulert to ensure the security of your dependencies. Regular monitoring and updates can help mitigate the risks associated with open-source vulnerabilities.
See every vulnerability recorded for erwin-kentang35-ruro →
FAQ
erwin-kentang35-ruro is an npm package that has been identified as part of a malicious campaign to manipulate the npm registry.
The malicious code can lead to the publication of unwanted packages, potentially compromising your project's security and integrity.
You should uninstall the erwin-kentang35-ruro package immediately and monitor your dependencies for any other vulnerabilities.
Yes, regularly update your dependencies, use trusted packages, and utilize tools like Vulert to monitor for vulnerabilities in your project.
Vulert is a tool that monitors and alerts in real-time for open-source vulnerabilities in your software. You can use it to check your package-lock.json for vulnerabilities without needing to install any software.
