Malicious Code Injection in utomo-kentang81-ruro Package
Summary
MAL-2025-110273: Malicious code in utomo-kentang81-ruro (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-kentang81-ruro 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-kentang81-ruro package originates from its involvement in a malicious campaign that floods the npm registry with derivative packages. The malicious payload modifies the package.json file to remove private flags, alters version numbers, and generates random package names, leading to the pollution of the npm registry. This can result in developers unknowingly using compromised packages, which may lead to security breaches and loss of trust in the npm ecosystem.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall utomo-kentang81-ruro
If 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 workaround, you can avoid using the utomo-kentang81-ruro package altogether. If it is already in use, consider removing it from your dependencies and replacing it with a trusted alternative package that serves the same purpose.
Conclusion
The utomo-kentang81-ruro package has been identified as containing malicious code that poses a significant risk to developers and the npm ecosystem. It is crucial to remove this package from your project and stay vigilant about the security of your dependencies.
See every vulnerability recorded for utomo-kentang81-ruro →
FAQ
The vulnerability can lead to the installation of compromised packages, which may contain malicious code that can affect your application's security and integrity.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. You can check your application using the Vulert playground without any signup.
It is advisable to remove the package from your project immediately and replace it with a trusted alternative.
Yes, you can look for alternative packages that provide similar functionality but have a proven track record of security.
Regularly check for updates to your packages and use tools like Vulert to monitor for vulnerabilities in your project's dependencies.