Malicious Code Injection in mahesa-ubi67-breki: A Threat to npm Ecosystem
Summary
MAL-2025-74321: Malicious code in mahesa-ubi67-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-ubi67-breki' is part of a series of npm packages associated with the tea.xyz token reward campaign. These packages are designed to manipulate the npm registry by automatically generating and publishing 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 in 'mahesa-ubi67-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, primarily themed around Indonesian culture, and continuously republishes these variants. This behavior can lead to pollution of the npm registry, making it difficult for developers to find legitimate packages and potentially exposing them to further malicious activities.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall mahesa-ubi67-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, you can avoid using the 'mahesa-ubi67-breki' package and monitor your project's dependencies for any signs of malicious activity. Regularly audit your npm packages using 'npm audit' to identify vulnerabilities.
Conclusion
The 'mahesa-ubi67-breki' package poses a significant risk due to its malicious code designed to manipulate the npm registry. It is crucial for developers to remove this package and monitor their dependencies to maintain the integrity of their applications.
See every vulnerability recorded for mahesa-ubi67-breki →
FAQ
The malicious code can lead to the pollution of the npm registry, making it harder for developers to find legitimate packages and potentially exposing them to further vulnerabilities.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check if your application is affected without requiring any signup.
If you have installed 'mahesa-ubi67-breki', you should uninstall it immediately using 'npm uninstall mahesa-ubi67-breki' and audit your project for any other vulnerabilities.
Currently, there are no patched versions available for 'mahesa-ubi67-breki'. It is recommended to remove the package entirely.
Regularly audit your dependencies using 'npm audit', stay informed about vulnerabilities in the npm ecosystem, and consider using tools like Vulert for real-time monitoring.
