Malicious Code Injection in joko-toge36-ruro Package: npm Vulnerability Overview
Summary
MAL-2025-104656: Malicious code in joko-toge36-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-toge36-ruro package is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to facilitate the automatic generation and publication of derivative packages, which can inflate developer reputation scores for token rewards. However, it has been identified as containing malicious code that compromises its integrity.
Vulnerability Detail
The vulnerability originates from the malicious intent behind the package, which includes scripts that modify the package.json file to remove private flags, alter version numbers, and generate random package names. This behavior leads to the continuous republishing of variants, polluting the npm registry and potentially damaging the reputation of legitimate developers. The malicious payload can also lead to unintended consequences for users who inadvertently install these compromised packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall joko-toge36-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 workaround, avoid using the joko-toge36-ruro package and monitor your project for any dependencies that may have included it. You can also use the following command to check for vulnerabilities in your project: npm audit.
Conclusion
The joko-toge36-ruro package has been identified as containing malicious code that compromises its integrity and can lead to significant issues for developers. It is crucial to remove this package from your projects and monitor for any dependencies that may be affected. Utilizing tools like Vulert can help in maintaining the security of your applications.
See every vulnerability recorded for joko-toge36-ruro →
FAQ
The malicious code can lead to the modification of your project's package.json file, potentially exposing it to further vulnerabilities and damaging your project's integrity.
You can use tools like Vulert, which monitors your package-lock.json file for vulnerabilities in real-time. You can also check your application using the Vulert playground without any signup.
Immediately uninstall the joko-toge36-ruro package using the command: npm uninstall joko-toge36-ruro, and review your project for any dependencies that may be affected.
Yes, consider looking for other packages that provide similar functionality without the associated risks. Always verify the package's reputation and reviews before installation.
Regularly audit your dependencies using npm audit, and consider using tools like Vulert to monitor for vulnerabilities in real-time.
