Malicious Code Injection in joko-dodol68-breki Package
Summary
MAL-2025-73686: Malicious code in joko-dodol68-breki (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-dodol68-breki package is part of the npm ecosystem, often used in JavaScript applications. It is associated with the tea.xyz token reward campaign, which has been known to flood the npm registry with packages that inflate developer reputation scores. This package, like others in the campaign, is designed to automatically generate and publish derivative packages, which can lead to significant pollution of the npm registry.
Vulnerability Detail
The vulnerability in the joko-dodol68-breki package stems from its malicious code that modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior is intended to create numerous derivative packages that can mislead developers and inflate reputation scores for token rewards. The malicious payload can lead to unintentional exposure of sensitive information and can compromise the integrity of the npm registry.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall joko-dodol68-brekiIf 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 prevent the installation of the vulnerable package by using npm's package-lock.json to lock down your dependencies. Additionally, you can use the following command to uninstall the package: npm uninstall joko-dodol68-breki.
Conclusion
The joko-dodol68-breki package contains malicious code that poses a significant risk to developers and the integrity of the npm registry. It is crucial to remove this package and monitor your dependencies for vulnerabilities. Utilizing tools like Vulert can help you stay informed and secure.
See every vulnerability recorded for joko-dodol68-breki →
FAQ
The vulnerability can lead to the exposure of sensitive information and the pollution of the npm registry with malicious packages.
You can use Vulert to monitor and alert for open-source vulnerabilities in your software. Visit Vulert Scanner to check your application without any signup.
You should uninstall the joko-dodol68-breki package immediately and check for any other dependencies that may be affected.
Regularly audit your dependencies and use tools like Vulert to monitor for vulnerabilities in real-time.
Look for unexpected changes in your package.json file, unusual package names, or an increase in the number of installed packages without your knowledge.
