Malicious Code Injection in utomo-soto4-breki Package - npm Vulnerability
Summary
MAL-2025-75941: Malicious code in utomo-soto4-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
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
Background
The utomo-soto4-breki package is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to facilitate the automatic generation and publication of derivative packages, which can inflate developer reputation scores for token rewards. However, it has been identified as containing malicious code that compromises its integrity and the security of the npm registry.
Vulnerability Detail
The vulnerability in the utomo-soto4-breki package originates from its malicious payload, which 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 affecting other packages and developers. The malicious scripts included (auto.js, autopublish.js, etc.) are designed to automate this process, making it difficult to track and mitigate the impact.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall utomo-soto4-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-soto4-breki package from your project by executing the command: 'npm uninstall utomo-soto4-breki'. This will prevent the malicious code from executing until a patched version is available.
Conclusion
The utomo-soto4-breki package has been identified as containing malicious code that poses a significant risk to the npm ecosystem. It is crucial for developers to take immediate action by updating or removing the package to safeguard their applications and the integrity of the npm registry.
See every vulnerability recorded for utomo-soto4-breki →
FAQ
The vulnerability involves malicious code that modifies package.json and republishes variants to pollute the npm registry.
You can use Vulert, which monitors open-source vulnerabilities in real-time. Visit Vulert Scanner to check your application without any signup.
As a temporary measure, uninstall the utomo-soto4-breki package to mitigate the risk until a patched version is available.
Yes, the malicious behavior can lead to the pollution of the npm registry, affecting other developers and packages.
The vulnerability was reported by Amazon Inspector, which specializes in identifying security issues in open-source packages.
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
