Malicious Code Injection in joko-kembang53-breki Package
Summary
MAL-2025-73709: Malicious code in joko-kembang53-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-kembang53-breki package is part of the npm ecosystem, which is widely used for managing JavaScript packages. This package has been identified as part of a malicious campaign that aims to exploit the npm registry by flooding it with derivative packages. These packages are designed to inflate developer reputation scores through automated publishing scripts, which can lead to significant pollution of the npm registry.
Vulnerability Detail
The vulnerability in the joko-kembang53-breki package stems from its association with a malicious campaign that modifies the package.json file to remove private flags and change version numbers. It generates random package names, often themed around Indonesian culture, and continuously republishes these variants. This behavior not only compromises the integrity of the npm registry but also poses a risk to developers who may unknowingly use these compromised packages, leading to potential 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-kembang53-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-kembang53-breki package and any other packages that are part of the malicious campaign. Regularly audit your package-lock.json file to identify and remove any suspicious packages.
Conclusion
The joko-kembang53-breki package has been identified as part of a malicious campaign that poses significant risks to developers and the integrity of the npm registry. It is essential to take immediate action by removing the package and monitoring your dependencies to ensure the security of your applications.
See every vulnerability recorded for joko-kembang53-breki →
FAQ
The malicious code can lead to the pollution of the npm registry and may compromise the security of applications that use these packages.
You can use the Vulert platform 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 package immediately and update your dependencies to ensure your application is secure.
Currently, the best course of action is to uninstall the compromised package. Keep an eye on the npm registry for any updates or patches.
Regularly audit your dependencies, use tools like Vulert for real-time monitoring, and stay informed about the latest security advisories in the open-source community.
