Malicious Code Injection in joko-getuk88-ruro Package
Summary
MAL-2025-104587: Malicious code in joko-getuk88-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-getuk88-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 publishing of derivative packages, which can inflate developer reputation scores in exchange for token rewards. However, it has been compromised to include malicious scripts that alter its functionality.
Vulnerability Detail
The vulnerability in the joko-getuk88-ruro package stems from its inclusion in a malicious campaign that modifies the package.json file to remove private flags, changes version numbers, and generates random package names. This behavior leads to the continuous republishing of variants, which pollutes the npm registry and can compromise the integrity of applications relying on this package. The malicious payload is executed through scripts named auto.js, autopublish.js, and others, which are designed to automate these harmful actions.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall joko-getuk88-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, you can remove the joko-getuk88-ruro package from your project by executing: npm uninstall joko-getuk88-ruro. This will prevent the execution of any malicious scripts associated with the package until a secure version is available.
Conclusion
The joko-getuk88-ruro package has been identified as containing malicious code that can compromise applications relying on it. It is crucial to update or remove this package to maintain the security and integrity of your software. Utilize tools like Vulert for ongoing monitoring of your dependencies.
See every vulnerability recorded for joko-getuk88-ruro →
FAQ
The vulnerability can lead to the pollution of the npm registry and compromise the integrity of applications that depend on this package.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check your application without needing to sign up.
If an immediate update is not possible, consider removing the package from your project as a temporary measure to mitigate risks.
While specific exploits have not been detailed, the malicious behavior of the package can lead to unauthorized modifications and potential data breaches.
Regularly monitor your dependencies for vulnerabilities using tools like Vulert and keep your packages updated to the latest secure versions.
