Malicious Code Injection in ruji-25: A Threat to npm Ecosystem
Summary
MAL-2025-165250: Malicious code in ruji-25 (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 'ruji-25' is part of the npm ecosystem, which is widely used for JavaScript package management. It is often utilized in various applications to manage dependencies and streamline development processes. However, this package has been identified as part of a malicious campaign that aims to manipulate the npm registry by flooding it with derivative packages, thereby compromising the integrity of the ecosystem.
Vulnerability Detail
The vulnerability in 'ruji-25' originates from its association with the tea.xyz token reward campaign. This package contains scripts designed to automatically generate and publish derivative packages with randomized names, which can inflate developer reputation scores. The malicious payload modifies the package.json file to remove private flags, alters version numbers, and continuously republishes variants, leading to pollution of the npm registry. This not only affects the reputation of legitimate developers but also poses security risks to applications relying on these packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall ruji-25
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 'ruji-25' package and any packages that depend on it. If you have already installed it, ensure to remove it from your project and monitor your package-lock.json for any unauthorized changes.
Conclusion
The 'ruji-25' package poses a significant threat to the npm ecosystem due to its malicious code designed to manipulate package reputation and pollute the registry. Immediate action is required to remove this package and safeguard your projects from potential security risks. Utilizing tools like Vulert can help in monitoring and managing vulnerabilities effectively.
See every vulnerability recorded for ruji-25 →
FAQ
The malicious code can lead to unauthorized changes in your project's dependencies, potentially compromising the security and integrity of your application.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software. Visit Vulert Scanner to check if your application is affected without requiring any installation.
You should uninstall the package immediately and review your project for any unauthorized changes made by the malicious scripts.
No official patches are available for ruji-25 as it is a malicious package. The best course of action is to remove it from your project.
Regularly audit your dependencies, use tools like Vulert for real-time monitoring, and stay informed about known vulnerabilities in the npm ecosystem.