Malicious Code Injection in indah-bakso66-breki: A Threat to npm Ecosystem
Summary
MAL-2025-73470: Malicious code in indah-bakso66-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 package 'indah-bakso66-breki' is part of a series of npm packages that were created as part of a token reward campaign. These packages are designed to manipulate the npm registry by generating and publishing numerous derivative packages with randomized names. This behavior not only inflates developer reputation scores but also poses a significant risk to the integrity of the npm ecosystem.
Vulnerability Detail
The vulnerability originates from malicious code embedded within the 'indah-bakso66-breki' package. This code modifies the package.json file to remove private flags, alters version numbers, and generates random package names, which leads to the continuous republishing of these variants. The ramifications include pollution of the npm registry, potential security risks for developers using these packages, and a compromised reputation system within the npm ecosystem.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall indah-bakso66-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 remove the 'indah-bakso66-breki' package from your project by executing: 'npm uninstall indah-bakso66-breki'. This will prevent any malicious code from executing until a fix is applied.
Conclusion
The 'indah-bakso66-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 remain vigilant, update their packages, and utilize tools like Vulert to monitor for vulnerabilities.
See every vulnerability recorded for indah-bakso66-breki →
FAQ
It is an npm package that is part of a malicious campaign to inflate developer reputation scores by flooding the npm registry with derivative packages.
The vulnerability can lead to the pollution of the npm registry and may expose your project to security risks if you inadvertently use affected packages.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check your application without any signup.
If an update is not available, consider removing the package from your project as a temporary measure until a fix is released.
Detailed information can be found in the vulnerability report on the Open Source Vulnerability database or by checking the package's repository.
