Malicious Code Injection in vida-kentang31-ruro Package

vida-kentang31-ruro Updated 18 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-110480: Malicious code in vida-kentang31-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 Devnack Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The vida-kentang31-ruro package is part of the npm ecosystem, which is widely used for JavaScript package management. This package is associated with the tea.xyz token reward campaign, which has been known to flood the npm registry with malicious packages. These packages often contain scripts that automatically generate and publish derivative packages, compromising the integrity of the npm ecosystem.

Vulnerability Detail

The vulnerability in the vida-kentang31-ruro package stems from its inclusion in a malicious campaign that modifies the package.json file to remove private flags and change version numbers. It generates random package names and continuously republishes variants, which pollutes the npm registry. This behavior can lead to a loss of trust in the npm ecosystem and can inflate developer reputation scores fraudulently.

How To Fix

This package is malicious. Remove it and rotate any credentials it could have accessed.

npm uninstall vida-kentang31-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 vida-kentang31-ruro package altogether. If it is already in use, consider replacing it with a reputable alternative that does not exhibit malicious behavior.

Conclusion

The vida-kentang31-ruro package poses a significant risk due to its malicious behavior of modifying package files and republishing variants. It is crucial for developers to be vigilant about the packages they use and to employ tools like Vulert to monitor for vulnerabilities. Removing this package and replacing it with a trusted alternative is essential to maintain the integrity of your project.

See every vulnerability recorded for vida-kentang31-ruro →

Share this vulnerability

FAQ

The vida-kentang31-ruro package is an npm package associated with a malicious campaign that generates and publishes derivative packages to inflate developer reputation scores.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software. By checking your package-lock.json file, you can identify if your project is affected.

The risks include potential loss of trust in the npm ecosystem, fraudulent inflation of developer reputation scores, and exposure to further malicious packages.

Regularly audit your dependencies and use tools like Vulert to monitor for vulnerabilities in real-time. Avoid using packages from untrusted sources.

Uninstall the vida-kentang31-ruro package immediately and check for any dependencies that may rely on it. Update your project to remove any references to this package.

How To Fix

This package is malicious. Remove it and rotate any credentials it could have accessed.

npm uninstall vida-kentang31-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