Malicious Code Injection in eko-lupis32-ruro Package - npm Vulnerability
Summary
MAL-2025-101961: Malicious code in eko-lupis32-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 eko-lupis32-ruro package is part of the npm ecosystem, which is widely used for JavaScript package management. This package, like many others, is intended to facilitate the development and distribution of JavaScript applications. However, it has been identified as part of a malicious campaign that aims to exploit the npm registry by flooding it with derivative packages that inflate developer reputation scores for token rewards.
Vulnerability Detail
The vulnerability originates from a malicious payload embedded within the eko-lupis32-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.) are designed to continuously republish these variants, thereby polluting the npm registry and potentially compromising the integrity of other packages. This poses significant risks, including the potential for developers to unknowingly install 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 eko-lupis32-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 workaround, you can avoid using the eko-lupis32-ruro package and look for alternative packages that provide similar functionality without the associated risks. Additionally, you can monitor your package-lock.json file for any unauthorized changes or installations.
Conclusion
The eko-lupis32-ruro package has been identified as a malicious entity within the npm ecosystem, posing significant risks to developers and their applications. Immediate action is required to remove this package and monitor for any unauthorized changes. Utilizing tools like Vulert can help maintain the security of your projects.
See every vulnerability recorded for eko-lupis32-ruro →
FAQ
eko-lupis32-ruro is an npm package that has been identified as part of a malicious campaign to exploit the npm registry.
The malicious code can modify your package.json file, remove security flags, and republish compromised packages, potentially leading to security vulnerabilities in your application.
You should uninstall the eko-lupis32-ruro package immediately using the command npm uninstall eko-lupis32-ruro.
Yes, you can use Vulert, which monitors your package-lock.json file for open-source vulnerabilities in real-time without requiring code access or installation.
You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.
