Malicious Code Injection in umi-papeda46-ruro Package

umi-papeda46-ruro Updated 18 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-109998: Malicious code in umi-papeda46-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 Devnack Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

The umi-papeda46-ruro package is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to facilitate token rewards for developers by generating and publishing derivative packages. However, it has been compromised, leading to significant security concerns.

Vulnerability Detail

The vulnerability in the umi-papeda46-ruro package stems from its malicious code, which modifies the package.json file to remove private flags and alters version numbers. It generates random package names, often themed around Indonesian culture, and continuously republishes these variants to the npm registry. This behavior not only inflates developer reputation scores but also pollutes the npm registry, potentially leading to the installation of compromised packages by unsuspecting developers.

How To Fix

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

npm uninstall umi-papeda46-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, avoid using the umi-papeda46-ruro package until a secure version is available. Regularly monitor your dependencies for any updates or patches that address this vulnerability.

Conclusion

The umi-papeda46-ruro package has been identified as containing malicious code that compromises the integrity of npm projects. It is essential to remove this package and monitor for updates or patches to safeguard your applications from potential threats.

See every vulnerability recorded for umi-papeda46-ruro →

Share this vulnerability

FAQ

The umi-papeda46-ruro package is part of a token reward campaign on npm, designed to help developers earn rewards by publishing packages.

The vulnerability allows malicious code to alter your project's package.json file, potentially leading to the installation of compromised packages and affecting your project's integrity.

If you have installed the umi-papeda46-ruro package, immediately uninstall it using 'npm uninstall umi-papeda46-ruro' and check for any other affected packages.

You can use Vulert, which monitors your package-lock.json file to alert you in real-time about open-source vulnerabilities. You can also check your application using the Vulert playground without any signup.

To prevent vulnerabilities, regularly update your dependencies, use tools like Vulert for monitoring, and review package sources before installation.

How To Fix

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

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