Malicious Code Injection in eko-kentang46-ruro Package
Summary
MAL-2025-101949: Malicious code in eko-kentang46-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-kentang46-ruro package is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to facilitate the automatic generation and publication of derivative packages, which can inflate developer reputation scores in exchange for token rewards. However, it has been identified as containing malicious code that compromises the integrity of the npm registry.
Vulnerability Detail
The vulnerability originates from the eko-kentang46-ruro package, which includes scripts that modify the package.json file to remove private flags, alter version numbers, and generate random package names. This malicious behavior leads to the continuous republishing of these variants, polluting the npm registry and potentially compromising other packages. The impact of this vulnerability includes the risk of developers unknowingly using compromised packages, which can lead to security breaches and loss of trust in the npm ecosystem.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall eko-kentang46-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 workaround, you can manually remove the eko-kentang46-ruro package from your project by running the command: npm uninstall eko-kentang46-ruro. Additionally, consider using tools like Vulert to monitor your package-lock.json for vulnerabilities.
Conclusion
The eko-kentang46-ruro package poses a significant security risk due to its malicious code that modifies package configurations and repopulates the npm registry with compromised packages. It is crucial for developers to remove this package and monitor their projects for vulnerabilities to maintain the integrity of their applications.
See every vulnerability recorded for eko-kentang46-ruro →
FAQ
It is an npm package associated with the tea.xyz token reward campaign, designed to generate and publish derivative packages.
The vulnerability can lead to the inclusion of malicious code in your project, potentially compromising its security and integrity.
You should uninstall the eko-kentang46-ruro package immediately and monitor your project for any other vulnerabilities.
You can use Vulert, which monitors your package-lock.json for open-source vulnerabilities in real-time without requiring installation.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without signing up.
