Malicious Code Injection in eka-ragi72-ruro: A Threat to npm Ecosystem
Summary
MAL-2025-101927: Malicious code in eka-ragi72-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-ragi72-ruro' is part of a series of malicious packages that emerged during the tea.xyz token reward campaign. These packages are designed to manipulate the npm registry by automatically generating and publishing derivative packages with randomized names. This behavior is intended to inflate developer reputation scores for token rewards, posing a significant risk to the integrity of the npm ecosystem.
Vulnerability Detail
The vulnerability in 'eka-ragi72-ruro' originates from its malicious code, which modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This allows the package to continuously republish variants, polluting the npm registry and potentially leading to the distribution of compromised software. The malicious payload is particularly concerning as it undermines the trustworthiness of the npm ecosystem and can affect developers relying on these packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall eka-ragi72-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 temporarily avoid using the 'eka-ragi72-ruro' package by removing it from your dependencies. Additionally, consider using alternative packages that provide similar functionality without the associated risks.
Conclusion
The 'eka-ragi72-ruro' package poses a significant threat to the npm ecosystem due to its malicious code designed to manipulate the registry. It is crucial for developers to remove this package and monitor their projects for vulnerabilities using tools like Vulert. Staying informed and proactive is essential to maintaining the security of your software.
See every vulnerability recorded for eka-ragi72-ruro →
FAQ
The main threat is the malicious code that modifies package.json files and floods the npm registry with derivative packages, compromising the integrity of the ecosystem.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check your application without needing to sign up.
Immediately remove the package from your project and check for any updates or patches that may address the vulnerability.
Yes, consider using other reputable packages that provide similar functionality without the associated risks of malicious behavior.
If you face issues, review your project's dependencies and ensure that no other malicious packages are present. You may also want to consult the npm documentation for further guidance.
