Malicious Code Injection in kurnia-ubi85-ruro: A Threat to npm Packages

kurnia-ubi85-ruro Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-104927: Malicious code in kurnia-ubi85-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 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 package 'kurnia-ubi85-ruro' is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to facilitate the automatic generation and publication of derivative packages, which can inflate developer reputation scores for token rewards. However, it has been identified as malicious due to its ability to modify package.json files and republish variants that can pollute the npm registry.

Vulnerability Detail

The vulnerability in 'kurnia-ubi85-ruro' originates from its malicious design, which includes scripts that remove private flags from package.json, alter version numbers, and generate random package names. This behavior can lead to the proliferation of unwanted packages in the npm registry, potentially compromising the integrity of the ecosystem and affecting developers who rely on these packages for their projects.

How To Fix

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

npm uninstall kurnia-ubi85-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 workaround, you can avoid using the 'kurnia-ubi85-ruro' package and look for alternative packages that provide similar functionality without the associated risks. Additionally, you can monitor your project for vulnerabilities using tools like Vulert, which can alert you to open-source vulnerabilities in real-time by analyzing your package-lock.json file.

Conclusion

The kurnia-ubi85-ruro package poses a significant risk due to its malicious code that alters package.json files and repopulates the npm registry with unwanted variants. It is crucial for developers to remove this package and monitor their projects for vulnerabilities using tools like Vulert to ensure the integrity of their software.

See every vulnerability recorded for kurnia-ubi85-ruro →

Share this vulnerability

FAQ

The main issue is that it contains malicious code that modifies package.json files and republish variants, leading to pollution of the npm registry.

You can use Vulert to check if your application is affected by this vulnerability without needing to access the code or install anything. Simply upload your package-lock.json file.

You should uninstall the package immediately using 'npm uninstall kurnia-ubi85-ruro' and look for alternative packages.

Regularly monitor your dependencies using tools like Vulert and keep your packages updated to the latest versions to minimize risks.

Using this package can lead to the proliferation of malicious packages in your project, which may compromise security and affect the functionality of your application.

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 kurnia-ubi85-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