Malicious Code Injection in joko-moci29-ruro Package: A Threat to npm Users
Summary
MAL-2025-104621: Malicious code in joko-moci29-ruro (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 joko-moci29-ruro 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 linked to a series of malicious activities aimed at inflating developer reputation scores through the automatic generation and publication of derivative packages. The package's functionality is compromised due to its malicious intent, making it a significant risk for developers and users relying on npm for package management.
Vulnerability Detail
The vulnerability in the joko-moci29-ruro package originates from its design to include malicious scripts that modify the package.json file. These scripts remove private flags, alter version numbers, and generate random package names, which leads to the continuous republishing of variants that pollute the npm registry. This not only affects the integrity of the npm ecosystem but also poses risks to developers who may unknowingly install these compromised packages, potentially leading to further exploitation.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall joko-moci29-ruroIf 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 joko-moci29-ruro package and any other packages associated with the tea.xyz token reward campaign. Regularly audit your package dependencies using tools like npm audit to identify and mitigate potential vulnerabilities.
Conclusion
The joko-moci29-ruro package poses a significant threat to the npm ecosystem due to its malicious code designed to manipulate package metadata and inflate developer reputation scores. It is crucial for developers to be vigilant, remove any affected packages, and utilize tools like Vulert for ongoing monitoring of vulnerabilities.
See every vulnerability recorded for joko-moci29-ruro →
FAQ
The joko-moci29-ruro package is an npm package that has been identified as malicious, associated with a campaign to inflate developer reputation scores through automated package publishing.
The vulnerability can lead to the installation of compromised packages, which may alter your project's dependencies and introduce security risks.
You should immediately uninstall the joko-moci29-ruro package and check for any other affected packages in your project.
You can use tools like Vulert, which monitors your package-lock.json file to alert you in real-time about open-source vulnerabilities in your software.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without requiring any signup.
