Malicious Code Injection in utomo-kentang81-ruro Package

utomo-kentang81-ruro Updated 18 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-110273: Malicious code in utomo-kentang81-ruro (npm). Affected versions are not published. No fix is published. How to fix ↓

Free scan

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.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

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 →

Share this vulnerability

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.

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 →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback