Malicious Code Injection in mahesa-dodol17-breki Package
Summary
MAL-2025-74275: Malicious code in mahesa-dodol17-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-dodol17-breki package is part of the npm ecosystem, typically used for various JavaScript applications. However, this package has been identified as part of a malicious campaign that floods the npm registry with derivative packages. The primary function of this package has been compromised, leading to significant security concerns for developers using it.
Vulnerability Detail
The vulnerability stems from malicious code embedded within the mahesa-dodol17-breki package. This code is designed to modify the package.json file by removing private flags, altering version numbers, and generating random package names. The intent is to inflate developer reputation scores for token rewards associated with the tea.xyz protocol. The continuous republishing of these variants pollutes the npm registry, potentially leading to further exploitation and security risks for users of the affected package.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall mahesa-dodol17-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-dodol17-breki package and look for alternative packages that provide similar functionality without the associated risks.
Conclusion
The mahesa-dodol17-breki package poses a significant security risk due to its malicious code designed to manipulate package metadata and inflate developer reputation scores. It is crucial for developers to uninstall this package, monitor their applications for vulnerabilities, and seek alternatives to ensure the security of their projects.
See every vulnerability recorded for mahesa-dodol17-breki →
FAQ
It is an npm package that has been identified as part of a malicious campaign to inflate developer reputation scores through the creation of derivative packages.
The malicious code can compromise your application's integrity by modifying essential files and potentially leading to further security issues.
You should uninstall the package immediately and look for alternatives. Regularly check for updates from trusted sources.
Yes, you can use tools like Vulert, which monitors your package-lock.json file for open-source vulnerabilities in real-time.
Yes, you can use the Vulert playground at Vulert Scanner to check for vulnerabilities in your application without requiring an account.
