Malicious Code Injection in umi-rangi63-riris Package

umi-rangi63-riris Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-91485: Malicious code in umi-rangi63-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 Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

Background

The umi-rangi63-riris package is part of the npm ecosystem, which is widely used for JavaScript development. This package is associated with the tea.xyz token reward campaign, which has been known to flood the npm registry with malicious packages. The primary functionality of this package is to facilitate token rewards, but it has been compromised to include harmful scripts that manipulate package metadata.

Vulnerability Detail

The vulnerability in the umi-rangi63-riris package stems from its inclusion in a campaign that deploys malicious code designed to inflate developer reputation scores through the automatic generation and publication of derivative packages. This malicious payload alters the package.json file by removing private flags, changing version numbers, and generating random package names. As a result, it can lead to pollution of the npm registry, making it difficult for developers to find legitimate packages and potentially exposing their applications to further vulnerabilities.

How To Fix

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

npm uninstall umi-rangi63-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 avoid using the umi-rangi63-riris package altogether and look for alternative packages that provide similar functionality without the associated risks. Additionally, you can monitor your package dependencies using tools like Vulert, which can alert you to vulnerabilities in real-time.

Conclusion

The umi-rangi63-riris package has been identified as containing malicious code that can compromise your application and pollute the npm registry. It is crucial to remove this package and monitor your dependencies for vulnerabilities using tools like Vulert. Staying informed and proactive can help protect your projects from potential threats.

See every vulnerability recorded for umi-rangi63-riris →

Share this vulnerability

FAQ

The umi-rangi63-riris package is part of the npm ecosystem and is associated with a token reward campaign that has been compromised to include malicious code.

The malicious code modifies your package.json file, potentially leading to the publication of harmful packages and pollution of the npm registry.

You should uninstall the umi-rangi63-riris package immediately and check for any other compromised packages in your project.

You can use Vulert, which monitors your package-lock.json file to alert you in real-time for open-source vulnerabilities without requiring code access.

Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.

Sponsored Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

How To Fix

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

npm uninstall umi-rangi63-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