Malicious Code Injection in eka-kue45-ruro: A Threat to npm Packages
Summary
MAL-2025-101914: Malicious code in eka-kue45-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 'eka-kue45-ruro' is part of the npm ecosystem, which is widely used for JavaScript package management. This package is associated with the tea.xyz token reward campaign, which has been known to flood the npm registry with malicious packages. These packages are designed to manipulate developer reputation scores by automatically generating and publishing derivative packages with altered names and contents.
Vulnerability Detail
The vulnerability in 'eka-kue45-ruro' involves the presence of malicious code that modifies the package.json file to remove private flags, changes version numbers, and generates random package names. This behavior is intended to inflate the reputation of developers participating in the tea protocol token rewards. The malicious payload continuously republishes variants, leading to pollution of the npm registry and potential security risks for users who inadvertently install these packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall eka-kue45-ruro
If 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 'eka-kue45-ruro' package and any other packages associated with the tea.xyz token reward campaign. Monitor your package-lock.json file for any unauthorized changes or additions.
Conclusion
The 'eka-kue45-ruro' package poses a significant threat due to its malicious code designed to manipulate npm registry entries. Users are advised to uninstall this package and monitor their dependencies closely to maintain the integrity of their projects.
See every vulnerability recorded for eka-kue45-ruro →
FAQ
The main issue is the presence of malicious code that modifies package.json files and republishes variants to manipulate developer reputation scores.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software. Check your package-lock.json file using the Vulert playground at Vulert Scanner.
Immediately uninstall the package using 'npm uninstall eka-kue45-ruro' and review your project dependencies for any other suspicious packages.
Yes, the vulnerability can lead to the pollution of the npm registry and may compromise the security of projects that unknowingly depend on these malicious packages.
There is no patch for the 'eka-kue45-ruro' package itself. The recommended action is to remove the package entirely from your project.