Malicious Code Injection in joko-bakso77-breki Package
Summary
MAL-2025-73678: Malicious code in joko-bakso77-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-bakso77-breki package is part of the npm ecosystem, typically used for various JavaScript functionalities. However, it has been identified as part of a malicious campaign that floods the npm registry with derivative packages. This package is designed to manipulate developer reputation scores through automated publishing scripts.
Vulnerability Detail
The vulnerability in the joko-bakso77-breki package stems from its association with the tea.xyz token reward campaign. The package contains scripts that automatically generate and publish derivative packages with randomized names, modifying the package.json file to remove private flags and change version numbers. This behavior can lead to pollution of the npm registry, making it difficult for developers to find legitimate packages and potentially exposing them to further malicious activities.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall joko-bakso77-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 measure, you can avoid using the joko-bakso77-breki package altogether. If it is already in use, consider removing it from your project by executing: npm uninstall joko-bakso77-breki. Additionally, you can monitor your project for vulnerabilities using tools like Vulert, which can analyze your package-lock.json file for any known issues.
Conclusion
The joko-bakso77-breki package poses a significant risk due to its malicious code that alters package metadata and floods the npm registry. It is crucial for developers to stay informed about such vulnerabilities, regularly update their dependencies, and utilize tools like Vulert for real-time monitoring.
See every vulnerability recorded for joko-bakso77-breki →
FAQ
The main issue is that it contains malicious code that modifies package.json and floods the npm registry with derivative packages.
You can use Vulert's playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.
Using this package can lead to the pollution of the npm registry, making it harder to find legitimate packages and increasing the risk of further malicious attacks.
Regularly updating your dependencies and using tools like Vulert to monitor vulnerabilities can help prevent similar issues.
If you have already installed the package, you should uninstall it immediately and check for any other affected packages in your project.
