Malicious Code Injection in ruji-21 Package: A Threat to npm Users
Summary
MAL-2025-165246: Malicious code in ruji-21 (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 ruji-21 package is part of the npm ecosystem, often utilized in JavaScript projects for various functionalities. However, it has been identified as part of a malicious campaign that aims to exploit developers by flooding the npm registry with derivative packages. This package is particularly vulnerable due to its association with the tea.xyz token reward scheme, which incentivizes the creation of numerous fake packages to inflate developer reputation scores.
Vulnerability Detail
The vulnerability in the ruji-21 package stems from its malicious code that modifies the package.json file. This code removes private flags, alters version numbers, and generates random package names, leading to continuous republishing of these variants. The origin of this vulnerability is linked to the tea.xyz token reward campaign, which aims to manipulate the npm registry by creating a polluted environment filled with derivative packages. The ramifications include potential security risks for developers who unknowingly install these malicious packages, as well as damage to the integrity of the npm registry.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall ruji-21If 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 the ruji-21 package and look for alternative packages that provide similar functionality without the associated risks. Additionally, regularly audit your dependencies using tools like npm audit to identify and mitigate vulnerabilities.
Conclusion
The ruji-21 package poses a significant threat to npm users due to its malicious code that alters project configurations and floods the npm registry. It is crucial for developers to be vigilant, remove affected packages, and utilize tools to monitor their dependencies for vulnerabilities.
See every vulnerability recorded for ruji-21 →
FAQ
The ruji-21 package is an npm package that has been identified as part of a malicious campaign to flood the npm registry with fake packages.
The malicious code modifies your package.json file, potentially leading to security vulnerabilities and the pollution of your project's dependency tree.
You should uninstall the ruji-21 package immediately using 'npm uninstall ruji-21' and check for any other affected packages.
You can use tools like npm audit or services like Vulert, which monitors your package-lock.json for vulnerabilities in real-time.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.
