Malicious Code Injection in ruji-43: A Threat to npm Ecosystem
Summary
MAL-2025-165270: Malicious code in ruji-43 (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-43 package is part of the npm ecosystem, which is widely used for JavaScript package management. This package is associated with the tea.xyz token reward campaign, which has been known to flood npm with malicious packages. The primary function of ruji-43 is to facilitate the automatic generation and publication of derivative packages, which can inflate developer reputation scores in exchange for token rewards. However, its malicious behavior poses significant risks to developers and the integrity of the npm registry.
Vulnerability Detail
The vulnerability in ruji-43 originates from its design to include malicious scripts that modify the package.json file. These scripts remove private flags, alter version numbers, and create random package names, leading to the continuous republishing of variants that pollute the npm registry. This behavior can compromise the security of applications relying on these packages, potentially introducing further vulnerabilities and undermining developer trust in the npm ecosystem.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall ruji-43If 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-43 package and look for alternative packages that provide similar functionality without the associated risks. Additionally, you can monitor your package-lock.json file for any unauthorized changes.
Conclusion
The ruji-43 package poses a significant threat to the npm ecosystem due to its malicious behavior of modifying package files and republishing variants. It is essential 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-43 →
FAQ
Ruji-43 is an npm package that is part of a malicious campaign aimed at inflating developer reputation scores through the automatic generation of derivative packages.
The vulnerability can lead to unauthorized modifications in your package.json file, potentially introducing security risks and compromising the integrity of your application.
You should uninstall the ruji-43 package immediately using 'npm uninstall ruji-43' and review your project for any other potentially malicious packages.
You can use tools like Vulert, which monitors your package-lock.json for open-source vulnerabilities in real-time. You can check your application for vulnerabilities using the Vulert playground without any signup.
Yes, consider using other reputable npm packages that offer similar functionalities without the associated risks of malicious behavior.
