Malicious Code Injection in mahesa-mangut13-breki Package
Summary
MAL-2025-74291: Malicious code in mahesa-mangut13-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 mahesa-mangut13-breki package is part of the npm ecosystem, often used in JavaScript projects for various functionalities. However, it has been identified as part of a malicious campaign that floods the npm registry with derivative packages. These packages are designed to inflate developer reputation scores through automated publishing scripts, making them a significant risk for developers relying on npm for package management.
Vulnerability Detail
The vulnerability in the mahesa-mangut13-breki package stems from its association with a malicious campaign that modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior leads to the continuous republishing of variants, polluting the npm registry and potentially compromising the integrity of projects that depend on this package. The malicious payload can also lead to unintended exposure of sensitive information and increase the risk of dependency confusion attacks.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall mahesa-mangut13-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 avoid using the mahesa-mangut13-breki package and look for alternative packages that provide similar functionality without the associated risks. You can also use tools like Vulert to monitor your package-lock.json for vulnerabilities in real-time.
Conclusion
The mahesa-mangut13-breki package poses a significant risk due to its malicious code that modifies project configurations and repopulates the npm registry with harmful variants. Developers should take immediate action to remove this package and utilize monitoring tools like Vulert to safeguard their projects against such vulnerabilities.
See every vulnerability recorded for mahesa-mangut13-breki →
FAQ
The mahesa-mangut13-breki package is an npm package that has been identified as part of a malicious campaign aimed at inflating developer reputation scores.
The vulnerability can lead to the pollution of the npm registry, potential exposure of sensitive information, and increased risk of dependency confusion attacks.
You should uninstall the mahesa-mangut13-breki package immediately and monitor your project for any other vulnerable dependencies.
You can use Vulert, which allows you to monitor and alert in real-time for open-source vulnerabilities using just your package-lock.json file.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without requiring any signup.
