Malicious Code Exploit in tiara-kue34-ruro Package: npm Vulnerability Overview

tiara-kue34-ruro Updated 18 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-109671: Malicious code in tiara-kue34-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 tiara-kue34-ruro package is part of a broader campaign associated with the tea.xyz token reward initiative, which has been known to flood the npm ecosystem with malicious packages. These packages are designed to manipulate developer reputation scores by automatically generating and publishing derivative packages with randomized names. This behavior not only compromises the integrity of the npm registry but also poses risks to developers who may unknowingly use these tainted packages.

Vulnerability Detail

The vulnerability in the tiara-kue34-ruro package originates from its inclusion in a malicious campaign that modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This results in the continuous republishing of these variants, which pollutes the npm registry and can lead to security risks for developers who rely on the integrity of the packages they use. The malicious payload is designed to inflate developer reputation scores for rewards, making it a significant concern for the npm ecosystem.

How To Fix

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

npm uninstall tiara-kue34-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 manually check your package-lock.json file for any references to tiara-kue34-ruro and remove it. Additionally, consider using Vulert to monitor your project for vulnerabilities. You can check if your application is affected by this vulnerability using the Vulert playground at https://vulert.com/scanner without any signup.

Conclusion

The tiara-kue34-ruro package represents a significant vulnerability within the npm ecosystem, stemming from malicious practices aimed at inflating developer reputation scores. It is crucial for developers to remain vigilant, remove affected packages, and utilize tools like Vulert to monitor for vulnerabilities in their projects.

See every vulnerability recorded for tiara-kue34-ruro →

Share this vulnerability

FAQ

The tiara-kue34-ruro package is part of a malicious campaign that aims to manipulate npm's package registry by flooding it with derivative packages.

Using the tiara-kue34-ruro package can compromise your project's integrity and security, as it may lead to the inclusion of malicious code in your application.

You should remove the tiara-kue34-ruro package from your project immediately to mitigate any potential risks.

While npm has measures in place, it is crucial for developers to actively monitor their dependencies and use tools like Vulert to stay informed about vulnerabilities.

Vulert is a tool that monitors and alerts for open-source vulnerabilities in your software using just the package-lock.json file. It provides real-time alerts without requiring code access or installation.

How To Fix

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

npm uninstall tiara-kue34-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