Malicious Code Injection in patria-kue24-ruro: A Threat to npm Ecosystem

patria-kue24-ruro Updated 18 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-106964: Malicious code in patria-kue24-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 package 'patria-kue24-ruro' is part of a series of npm packages that have been associated with the tea.xyz token reward campaign. These packages are designed to manipulate the npm registry by automatically generating and publishing derivative packages with randomized names. This behavior is intended to inflate developer reputation scores for rewards associated with the tea protocol, posing a significant risk to the integrity of the npm ecosystem.

Vulnerability Detail

The vulnerability in 'patria-kue24-ruro' originates from malicious code embedded within the package. This code modifies the package.json file by removing private flags, altering version numbers, and generating random package names, which leads to the continuous republishing of variants. This not only pollutes the npm registry but also undermines the trustworthiness of the ecosystem, potentially allowing for further exploitation by malicious actors.

How To Fix

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

npm uninstall patria-kue24-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 'patria-kue24-ruro' package until a secure version is released. Additionally, consider using the following command to uninstall the package: 'npm uninstall patria-kue24-ruro'.

Conclusion

The 'patria-kue24-ruro' package poses a significant threat due to its malicious code that manipulates the npm registry. It is essential to take immediate action by updating or uninstalling the package and utilizing tools like Vulert for ongoing vulnerability monitoring.

See every vulnerability recorded for patria-kue24-ruro →

Share this vulnerability

FAQ

The main issue is that it contains malicious code that modifies package.json and floods the npm registry with derivative packages.

You can use Vulert to monitor and alert for open-source vulnerabilities in your software. Visit Vulert Scanner to check your application without any signup.

Using compromised packages can lead to data breaches, unauthorized access, and overall instability in your application due to malicious modifications.

Regularly audit your dependencies, use tools like Vulert for real-time monitoring, and stay updated with security advisories related to your packages.

Immediately uninstall the package and monitor your application for any unusual behavior. Consider updating to a secure version if available.

How To Fix

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

npm uninstall patria-kue24-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