Malicious Code Injection in ruji-38 Package: A Threat to npm Ecosystem
Summary
MAL-2025-165264: Malicious code in ruji-38 (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
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
Background
The ruji-38 package is part of the npm ecosystem, which is widely used for JavaScript package management. 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 significant risks to developers and users alike.
Vulnerability Detail
The vulnerability in the ruji-38 package originates from its design to include autopublish scripts that modify the package.json file. This manipulation removes private flags, alters version numbers, and generates random package names, leading to the continuous republishing of these variants. The ramifications include pollution of the npm registry, potential security risks for users, and damage to 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-38If 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-38 package and any other packages that may be associated with the tea.xyz token reward campaign. Regularly audit your package.json and package-lock.json files to identify and remove any suspicious packages.
Conclusion
The ruji-38 package poses a significant threat to the npm ecosystem due to its malicious code designed to manipulate package metadata. It is crucial for developers to be vigilant, regularly audit their dependencies, and utilize tools like Vulert to monitor for vulnerabilities. Immediate action is required to uninstall the affected package and safeguard your projects.
See every vulnerability recorded for ruji-38 →
FAQ
The ruji-38 package is an npm package that has been identified as part of a malicious campaign aimed at manipulating package metadata for token rewards.
The vulnerability can lead to the pollution of the npm registry, potential security risks, and damage to your project's integrity by introducing malicious code.
You should uninstall the ruji-38 package immediately using 'npm uninstall ruji-38' and audit your dependencies for any other 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 signup.
Regularly audit your dependencies, use trusted sources for packages, and consider using automated tools like Vulert to monitor for vulnerabilities.
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
