Malicious Code Injection in utomo-oncom2-breki Package
Summary
MAL-2025-75924: Malicious code in utomo-oncom2-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-oncom2-breki package is part of the npm ecosystem, which is widely used for JavaScript package management. This package has been identified as part of a malicious campaign that aims to exploit the npm registry by flooding it with derivative packages. The malicious nature of this package lies in its ability to modify critical files and republish itself under various names, thereby affecting the integrity of the npm ecosystem.
Vulnerability Detail
The vulnerability in the utomo-oncom2-breki package stems from its inclusion in a malicious campaign associated with the tea.xyz token reward initiative. This package contains scripts that automatically generate and publish derivative packages with randomized names. The malicious payload alters the package.json file by removing private flags, changing version numbers, and continuously republishing variants, which can lead to reputation inflation for developers and pollution of the npm registry. This poses significant risks to developers relying on the integrity of the npm ecosystem.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall utomo-oncom2-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 prevent the installation of this package by using npm's package-lock.json file to lock your dependencies. Additionally, you can monitor your project for vulnerabilities using Vulert, which analyzes your package-lock.json file for any open-source vulnerabilities in real-time.
Conclusion
The utomo-oncom2-breki package poses a significant risk due to its malicious code designed to exploit the npm registry. It is essential to remove this package and monitor your project for vulnerabilities to maintain the integrity of your software development environment.
See every vulnerability recorded for utomo-oncom2-breki →
FAQ
utomo-oncom2-breki is an npm package that has been identified as part of a malicious campaign aimed at exploiting the npm registry.
This vulnerability can lead to the pollution of the npm registry and may compromise the integrity of your project's dependencies.
You should remove the utomo-oncom2-breki package from your project immediately and monitor for any updates or patches.
You can use Vulert to monitor your package-lock.json file for vulnerabilities without needing to access the code or install additional software.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.
