Malicious Code Injection in tomi-kue5-riris: npm Package Vulnerability

tomi-kue5-riris Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-91152: Malicious code in tomi-kue5-riris (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 Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The package 'tomi-kue5-riris' is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. It is designed to facilitate the automatic generation and publication of derivative packages, which can inflate developer reputation scores for rewards. This package is particularly vulnerable due to its incorporation of autopublish scripts that can manipulate package metadata.

Vulnerability Detail

The vulnerability in 'tomi-kue5-riris' stems from its malicious payload, which modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior leads to the continuous republishing of variants, polluting the npm registry and potentially compromising the integrity of other packages. The origin of this vulnerability is linked to the broader trend of malicious packages flooding the npm ecosystem, aimed at exploiting the token reward system.

How To Fix

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

npm uninstall tomi-kue5-riris

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 workaround, you can prevent the installation of this package by using npm's package-lock.json to monitor dependencies. Additionally, you can use the following command to audit your project for vulnerabilities: 'npm audit'. This will help identify any other potentially harmful packages.

Conclusion

The 'tomi-kue5-riris' package is compromised by malicious code that alters package metadata and floods the npm registry with variants. It is crucial to remove this package and monitor your dependencies to maintain application security. Utilizing tools like Vulert can help in identifying and mitigating such vulnerabilities effectively.

See every vulnerability recorded for tomi-kue5-riris →

Share this vulnerability

FAQ

The vulnerability involves malicious code that modifies package metadata and repackages it, leading to potential pollution of the npm registry.

You can use Vulert, which monitors open-source vulnerabilities in real-time. Visit Vulert Scanner to check your application without requiring any signup.

You should uninstall the package immediately using 'npm uninstall tomi-kue5-riris' and check for any other affected packages.

Regularly audit your dependencies using 'npm audit' and consider using tools like Vulert to monitor for vulnerabilities in real-time.

Failing to address this vulnerability could lead to compromised application integrity, exposure to further malicious packages, and potential security breaches.

How To Fix

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

npm uninstall tomi-kue5-riris

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