Malicious Code Injection in ruji-29: A Threat to npm Packages
Summary
MAL-2025-165254: Malicious code in ruji-29 (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-29' is part of the npm ecosystem, primarily used for JavaScript development. It is associated with the tea.xyz token reward campaign, which has been known to flood the npm registry with malicious packages. These packages often contain scripts designed to manipulate package metadata and inflate developer reputation scores, posing a significant risk to developers and users alike.
Vulnerability Detail
The vulnerability in 'ruji-29' originates from its inclusion in a malicious campaign that employs autopublish scripts to generate and publish derivative packages with randomized names. This manipulation modifies the package.json file by removing private flags, altering version numbers, and continuously republishing variants, which can lead to registry pollution and potential exploitation of unsuspecting developers who may unknowingly install these compromised packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall ruji-29If 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-29' and any other packages associated with the tea.xyz token reward campaign. Regularly audit your package dependencies and utilize tools like npm audit to identify and mitigate vulnerabilities.
Conclusion
The 'ruji-29' package poses a significant threat due to its malicious code designed to manipulate package metadata and inflate developer reputation scores. It is essential to remove this package and regularly audit your dependencies to maintain a secure development environment.
See every vulnerability recorded for ruji-29 →
FAQ
The main risk is that it can modify your project's package.json file, leading to the installation of potentially harmful packages and polluting the npm registry.
You can use the Vulert platform, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check if your application is affected without any signup.
Immediately uninstall 'ruji-29' using the command 'npm uninstall ruji-29' and review your project's dependencies for any other potentially malicious packages.
Yes, tools like npm audit and Vulert can help identify vulnerabilities in your npm packages and provide alerts for any issues.
Vulert is a monitoring tool that uses your package-lock.json to track and alert you in real-time for open-source vulnerabilities in your software, ensuring you stay informed about potential risks.
