Malicious Code Injection in ruji-46: A Threat to npm Packages
Summary
MAL-2025-165273: Malicious code in ruji-46 (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-46 is part of the npm ecosystem, which is widely used for JavaScript package management. It is designed to facilitate the sharing and reuse of code among developers. 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. This behavior not only affects the integrity of the npm ecosystem but also poses a significant risk to developers who may unknowingly use compromised packages.
Vulnerability Detail
The vulnerability in ruji-46 stems from its association with the tea.xyz token reward campaign, which has led to the creation of numerous malicious packages. These packages contain scripts that automatically modify the package.json file to remove private flags, alter version numbers, and generate random package names. This results in the continuous republishing of variants, which pollutes the npm registry and can mislead developers into using potentially harmful code. The malicious payload is designed to inflate developer reputation scores for token rewards, making it a serious concern for the integrity of the npm ecosystem.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall ruji-46If 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-46 and any other packages associated with the tea.xyz campaign. Additionally, regularly audit your dependencies using the command 'npm audit' to identify and address vulnerabilities in your project.
Conclusion
The discovery of malicious code in the ruji-46 package highlights the ongoing risks associated with open-source software. Developers must remain vigilant and proactive in managing their dependencies to protect their projects from potential threats. By following the recommended steps to remove the affected package and utilizing tools like Vulert, you can enhance your project's security.
See every vulnerability recorded for ruji-46 →
FAQ
ruji-46 is an npm package that has been identified as part of a malicious campaign to manipulate the npm registry.
The vulnerability can lead to the introduction of malicious code into your project, compromising its security and integrity.
You should uninstall ruji-46 immediately and audit your project for any other potentially affected packages.
You can use tools like Vulert, which monitors your package-lock.json for open-source vulnerabilities in real-time without requiring code access.
Yes, you can use the Vulert playground at Vulert Scanner to check for vulnerabilities in your application without any signup.
