Malicious Code Injection in ruji-17: A Threat to npm Packages
Summary
MAL-2025-165241: Malicious code in ruji-17 (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-17' is part of the npm ecosystem, which is widely used for JavaScript package management. It is often utilized in various applications to manage dependencies efficiently. However, 'ruji-17' has been identified as part of a malicious campaign that aims to inflate developer reputation scores through the automatic generation and publication of derivative packages. This vulnerability poses significant risks to developers and users alike, as it can lead to the pollution of the npm registry and the potential for malicious code execution.
Vulnerability Detail
The vulnerability in 'ruji-17' originates from its association with the tea.xyz token reward campaign, which has been flooding the npm registry with malicious packages. These packages contain scripts that modify the package.json file by removing private flags, changing version numbers, and generating random package names. The continuous republishing of these variants can lead to a compromised npm registry, making it difficult for developers to trust the packages they use. The malicious payload can also facilitate the execution of harmful code within applications that depend on these packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall ruji-17If 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-17' and any other packages associated with the tea.xyz campaign. Regularly audit your package-lock.json file to identify and remove any suspicious packages. You can also use the following command to check for vulnerabilities in your dependencies: 'npm audit'.
Conclusion
The 'ruji-17' package presents a significant security risk due to its malicious code and association with a harmful campaign. Developers must take immediate action to remove this package and ensure their projects are secure. Utilizing tools like Vulert can aid in monitoring for vulnerabilities and maintaining a secure development environment.
See every vulnerability recorded for ruji-17 →
FAQ
The vulnerability involves malicious code that modifies package.json files and floods the npm registry with derivative packages.
You can use tools like Vulert to monitor your package-lock.json for vulnerabilities. Visit Vulert Scanner to check your application without signing up.
You should uninstall ruji-17 immediately using the command 'npm uninstall ruji-17' and audit your project for other vulnerabilities.
Yes, the impacts include potential execution of malicious code, pollution of the npm registry, and compromised developer reputation.
Regularly audit your dependencies, use trusted packages, and stay updated on security advisories related to the npm ecosystem.
