Malicious Code Injection in vida-sate54-ruro Package

vida-sate54-ruro Updated 18 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-110505: Malicious code in vida-sate54-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 Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

The vida-sate54-ruro package is part of the npm ecosystem, often utilized in various JavaScript applications. It is associated with the tea.xyz token reward campaign, which has been known to flood the npm registry with numerous packages. This package, like others in the campaign, is designed to manipulate developer reputation scores through the automatic generation and publication of derivative packages.

Vulnerability Detail

The vulnerability in the vida-sate54-ruro package stems from its malicious code that modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior is intended to inflate developer reputation scores fraudulently and can lead to the pollution of the npm registry with numerous unwanted packages. The malicious payload can compromise the integrity of applications relying on this package, potentially leading to security risks and instability.

How To Fix

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

npm uninstall vida-sate54-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 temporary measure, you can avoid using the vida-sate54-ruro package altogether. If it is already in use, consider replacing it with a similar package that does not exhibit malicious behavior. Additionally, regularly audit your package dependencies to identify and remove any malicious packages.

Conclusion

The vida-sate54-ruro package contains malicious code that can compromise the integrity of applications. It is essential to remove this package and monitor your dependencies to ensure the security of your projects. Utilizing tools like Vulert can help in identifying and mitigating such vulnerabilities effectively.

See every vulnerability recorded for vida-sate54-ruro →

Share this vulnerability

FAQ

The vida-sate54-ruro package is an npm package associated with the tea.xyz token reward campaign, known for its malicious behavior.

The malicious code can compromise your application's integrity by polluting the npm registry and potentially introducing security risks.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Check your application using the Vulert playground without any signup.

Remove the vida-sate54-ruro package from your project and consider replacing it with a secure alternative.

Regularly audit your dependencies and use tools like Vulert to monitor for vulnerabilities in your open-source packages.

How To Fix

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

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