Malicious Code Injection in zain-bakso12-breki Package
Summary
MAL-2025-76491: Malicious code in zain-bakso12-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 zain-bakso12-breki package is part of the npm ecosystem, primarily used for JavaScript applications. It has been identified as part of a broader campaign that aims to exploit npm's package publishing system. This package, like others in the campaign, is designed to inflate developer reputation scores through the automatic generation and publication of derivative packages.
Vulnerability Detail
The vulnerability in the zain-bakso12-breki package stems from its malicious code that modifies the package.json file to remove private flags and alters version numbers. It generates random Indonesian-themed package names and continuously republishes variants, leading to pollution of the npm registry. This behavior can compromise the integrity of the npm ecosystem and potentially lead to security risks for applications relying on these packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall zain-bakso12-breki
If 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 workaround, you can temporarily prevent the use of this package by removing it from your dependencies and replacing it with a secure alternative if available. Additionally, monitor your package-lock.json file for any unauthorized changes.
Conclusion
The zain-bakso12-breki package contains malicious code that poses a significant risk to the npm ecosystem. It is crucial to remove this package from your projects and monitor for any unauthorized changes to your dependencies. Utilizing tools like Vulert can help maintain the security of your applications.
See every vulnerability recorded for zain-bakso12-breki →
FAQ
The zain-bakso12-breki package is an npm package that has been identified as part of a malicious campaign to inflate developer reputation scores.
This vulnerability can lead to the pollution of the npm registry, potentially introducing insecure packages into your application and compromising its integrity.
If you have installed the zain-bakso12-breki package, you should uninstall it immediately and check for any dependencies that may be affected.
Yes, you can use tools like Vulert, which monitors your package-lock.json file for open-source vulnerabilities in real-time without requiring code access.
You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.