Malicious Code Injection in Joko-Bubur17-Breki Package
Summary
MAL-2025-73684: Malicious code in joko-bubur17-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-bubur17-breki' package is part of the npm ecosystem, often utilized in JavaScript projects. This package has been identified as part of a larger malicious campaign associated with the tea.xyz token reward system. It is designed to automatically generate and publish derivative packages, which can lead to reputation inflation for developers involved in the tea protocol.
Vulnerability Detail
The vulnerability stems from the package's malicious code that modifies the package.json file by removing private flags and altering version numbers. It generates random package names, predominantly themed around Indonesian culture, and continuously republishes these variants to the npm registry. This behavior not only pollutes the registry but also poses risks to developers who may unknowingly use these compromised packages, potentially leading to security breaches in their applications.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall joko-bubur17-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 avoid using the 'joko-bubur17-breki' package and look for alternative packages that provide similar functionality without the associated risks. Additionally, consider using tools like Vulert to monitor your project for vulnerabilities.
Conclusion
The 'joko-bubur17-breki' package poses a significant risk due to its malicious behavior of modifying project files and republishing variants to the npm registry. It is essential to remove this package and monitor your project for vulnerabilities to maintain security.
See every vulnerability recorded for joko-bubur17-breki →
FAQ
It is an npm package that has been identified as part of a malicious campaign aimed at inflating developer reputation scores through automated publishing.
If you have this package installed, it can modify your project files and potentially lead to security issues by introducing malicious code.
You should uninstall the package immediately and monitor your project for any other vulnerabilities.
You can use tools like Vulert, which allows you to check your package-lock.json file for vulnerabilities without requiring installation.
Yes, you can use the Vulert playground at Vulert Scanner to check for vulnerabilities in your application without any signup.
