Malicious Code Vulnerability in ruji-44: Exploitation of npm Registry
Summary
MAL-2025-165271: Malicious code in ruji-44 (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-44' 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-44' has been identified as part of a malicious campaign that floods the npm registry with derivative packages, aimed at inflating developer reputation scores for token rewards. This vulnerability poses a significant risk to the integrity of the npm ecosystem.
Vulnerability Detail
The vulnerability in 'ruji-44' originates from its association with the tea.xyz token reward campaign. It contains malicious scripts that modify the package.json file by removing private flags, altering version numbers, and generating random package names. This results in the continuous republishing of these variants, which pollutes the npm registry and can lead to compromised developer accounts and reputations.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall ruji-44If 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 measure, you can avoid using the 'ruji-44' package and any of its derivatives. Additionally, consider using a package-lock.json file to lock your dependencies to known safe versions.
Conclusion
The 'ruji-44' package poses a significant risk due to its malicious code that exploits the npm registry. It is crucial for developers to be vigilant, remove affected packages, and utilize tools like Vulert to monitor for vulnerabilities in their applications.
See every vulnerability recorded for ruji-44 →
FAQ
The impact includes potential pollution of the npm registry and compromised developer reputations due to the automatic generation of malicious packages.
You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.
You should uninstall 'ruji-44' immediately using 'npm uninstall ruji-44' and check for any other affected packages.
Currently, there are no specific patches for 'ruji-44', but it is recommended to monitor for updates and use safe versions of packages.
Vulert monitors and alerts for open-source vulnerabilities in your software using just the package-lock.json file, ensuring real-time awareness of potential threats.
