Malicious Code Vulnerability in utomo-bubur52-breki Package
Summary
MAL-2025-75893: Malicious code in utomo-bubur52-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 utomo-bubur52-breki package is part of a larger ecosystem within the npm registry, often associated with token reward campaigns. These packages are designed to manipulate developer reputation scores by automatically generating and publishing derivative packages with randomized names. The malicious nature of this package lies in its ability to alter critical files and republish variants, which can lead to significant pollution of the npm registry.
Vulnerability Detail
The vulnerability originates from the package's design to include autopublish scripts that modify the package.json file by removing private flags and changing version numbers. This allows the package to generate random names, specifically Indonesian-themed, and continuously republish these variants. The ramifications include the potential for developers to unknowingly install compromised packages, leading to security risks and a polluted npm registry.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall utomo-bubur52-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 utomo-bubur52-breki package from your project by executing: npm uninstall utomo-bubur52-breki. This will prevent any malicious code from executing until a secure version is available.
Conclusion
The utomo-bubur52-breki package poses a significant security risk due to its malicious code designed to manipulate package metadata and republish variants. It is essential to stay vigilant, regularly update packages, and utilize tools like Vulert to monitor for vulnerabilities.
See every vulnerability recorded for utomo-bubur52-breki →
FAQ
The main issue is that it contains malicious code designed to manipulate package metadata and republish variants, which can compromise the integrity of the npm registry.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. By using the Vulert playground, you can check if your application is affected without any signup.
Using this package can lead to security vulnerabilities, as it may introduce malicious code into your application and pollute the npm registry with compromised packages.
To prevent similar vulnerabilities, regularly audit your dependencies, use tools like Vulert to monitor for vulnerabilities, and avoid using packages from untrusted sources.
If you have installed the utomo-bubur52-breki package, it is crucial to uninstall it immediately and check for any other affected packages in your project.
