Malicious Code Injection in mahesa-bubur66-breki: A Threat to npm Users
Summary
MAL-2025-74272: Malicious code in mahesa-bubur66-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 'mahesa-bubur66-breki' is part of a series of npm packages that emerged during the tea.xyz token reward campaign. These packages are designed to manipulate the npm registry by creating and publishing numerous derivative packages with randomized names. The primary functionality of these packages is to inflate developer reputation scores for token rewards, but they introduce significant security risks.
Vulnerability Detail
The vulnerability in 'mahesa-bubur66-breki' originates from its malicious code, which modifies the package.json file to remove private flags and alters version numbers. It generates random package names, often themed around Indonesian culture, and continuously republishes these variants to pollute the npm registry. This behavior not only compromises the integrity of the npm ecosystem but also poses risks to developers who may unknowingly install these malicious packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall mahesa-bubur66-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, avoid using the 'mahesa-bubur66-breki' package and monitor your project for any unauthorized changes to your package.json file. Regularly audit your dependencies using tools like npm audit to identify and mitigate potential vulnerabilities.
Conclusion
The 'mahesa-bubur66-breki' package poses a significant security risk due to its malicious code that alters package.json files and floods the npm registry. Developers should take immediate action to remove this package and monitor their projects for vulnerabilities. Utilizing tools like Vulert can aid in maintaining a secure development environment.
See every vulnerability recorded for mahesa-bubur66-breki →
FAQ
The main threat is the malicious code that modifies package.json files and floods the npm registry with unauthorized packages, potentially compromising the integrity of your project.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software. Visit Vulert Scanner to check if your application is affected without any signup.
If you have installed 'mahesa-bubur66-breki', you should uninstall it immediately using 'npm uninstall mahesa-bubur66-breki' and review your project for any unauthorized changes.
Yes, tools like npm audit can help you identify vulnerabilities in your dependencies, and Vulert provides real-time monitoring for open-source vulnerabilities.
Using compromised packages can lead to security breaches, data loss, and damage to your project's reputation. It's crucial to regularly audit and maintain your dependencies.
