Malicious Code in Joko-Ubi10-Ruro: A Threat to npm Packages

joko-ubi10-ruro Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-104659: Malicious code in joko-ubi10-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

Joko-Ubi10-Ruro is an npm package that has been implicated in a malicious campaign targeting the npm registry. This package is part of a broader initiative associated with the tea.xyz token reward system, which aims to inflate developer reputation scores through the automatic generation and publication of derivative packages. The malicious nature of this package lies in its ability to modify its own metadata and continuously republish variants, thereby polluting the npm ecosystem.

Vulnerability Detail

The vulnerability in Joko-Ubi10-Ruro arises from its inclusion in a malicious campaign that utilizes autopublish scripts to generate and publish numerous derivative packages with randomized names. This behavior not only compromises the integrity of the npm registry but also poses a risk to developers who may unknowingly install these malicious packages. The payload modifies the package.json file to remove private flags, alters version numbers, and creates random package names, leading to potential security breaches and reputational damage for developers.

How To Fix

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

npm uninstall joko-ubi10-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 affected package and look for alternative packages that provide similar functionality without the associated risks. Always verify the source and integrity of packages before installation.

Conclusion

The Joko-Ubi10-Ruro package poses a significant risk due to its involvement in a malicious npm campaign. It is crucial for developers to be vigilant about the packages they use and to take immediate action to remove any affected packages. Regular monitoring and updating of dependencies can help mitigate such vulnerabilities.

See every vulnerability recorded for joko-ubi10-ruro →

Share this vulnerability

FAQ

Joko-Ubi10-Ruro is an npm package involved in a malicious campaign that aims to inflate developer reputation scores through the automatic generation of derivative packages.

The vulnerability can lead to the installation of malicious packages that may compromise your project's security and integrity, potentially exposing sensitive data or causing reputational harm.

You should immediately uninstall the package using npm uninstall joko-ubi10-ruro and review your project's dependencies for any other potentially malicious packages.

Yes, you can use Vulert, which monitors and alerts for open-source vulnerabilities in your software using just the package-lock.json file. You can check your application for vulnerabilities without any signup at the Vulert playground.

If you discover other vulnerabilities, follow the same steps: uninstall affected packages, update to patched versions if available, and consider using alternative packages.

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 joko-ubi10-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