Malicious Code Injection in ruji-41: A Threat to npm Ecosystem
Summary
MAL-2025-165268: Malicious code in ruji-41 (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-41' is part of the npm ecosystem, which is widely used for JavaScript package management. It is often utilized by developers to share and manage code libraries. However, 'ruji-41' has been identified as part of a malicious campaign that aims to exploit the npm registry by flooding it with derivative packages that can inflate developer reputation scores for token rewards. This vulnerability poses a significant risk to developers and users relying on npm packages.
Vulnerability Detail
The vulnerability in 'ruji-41' originates from its association with the tea.xyz token reward campaign. It contains malicious scripts that modify the package.json file to remove private flags, alter version numbers, and generate random package names. This behavior leads to the continuous republishing of variants, polluting the npm registry and potentially compromising the integrity of other packages. The malicious payload can affect the reputation of developers and lead to the distribution of unsafe code.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall ruji-41If 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 'ruji-41' and any packages that depend on it. Regularly audit your package-lock.json file to identify and remove any potentially malicious packages.
Conclusion
The 'ruji-41' package poses a significant threat to the npm ecosystem due to its malicious code that modifies package metadata and floods the registry with unsafe packages. It is essential for developers to be vigilant, remove this package, and utilize tools like Vulert to monitor for vulnerabilities in their projects.
See every vulnerability recorded for ruji-41 →
FAQ
The 'ruji-41' vulnerability can lead to the pollution of the npm registry, affecting the integrity of other packages and potentially compromising the security of applications that rely on them.
You can use the Vulert playground at Vulert Scanner to check if your application is affected by the 'ruji-41' vulnerability without requiring any signup.
If you have installed 'ruji-41', you should uninstall it immediately using 'npm uninstall ruji-41' and audit your project for any other malicious packages.
There are no patches available for 'ruji-41' as it is a malicious package. The best course of action is to remove it from your project.
To prevent similar vulnerabilities, regularly audit your dependencies, use trusted packages, and employ tools like Vulert to monitor for open-source vulnerabilities in real-time.
