Malicious Code Injection in qori-mie53-ruro Package - npm Vulnerability

qori-mie53-ruro Updated 18 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-107593: Malicious code in qori-mie53-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 Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The qori-mie53-ruro package is part of the npm ecosystem, which is widely used for JavaScript package management. This package is associated with the tea.xyz token reward campaign, which has been linked to a series of malicious activities aimed at inflating developer reputation scores. The package's functionality is compromised due to its involvement in autopublishing scripts that generate and publish derivative packages with randomized names, leading to potential pollution of the npm registry.

Vulnerability Detail

The vulnerability in the qori-mie53-ruro package originates from its design to include malicious autopublish scripts. These scripts modify the package.json file by removing private flags, altering version numbers, and creating random package names, which can lead to the proliferation of untrusted packages in the npm registry. This not only affects the integrity of the npm ecosystem but also poses security risks to developers who may unknowingly use these compromised packages.

How To Fix

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

npm uninstall qori-mie53-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 qori-mie53-ruro package and monitor your dependencies for any instances of this package. Additionally, consider using tools like Vulert to scan your project for vulnerabilities. You can use the following command to check your package-lock.json file: vulert scan package-lock.json.

Conclusion

The qori-mie53-ruro package poses a significant risk due to its malicious code that modifies package metadata and publishes untrusted variants. It is crucial for developers to remove this package and utilize tools like Vulert to ensure their projects remain secure from such vulnerabilities.

See every vulnerability recorded for qori-mie53-ruro →

Share this vulnerability

FAQ

The qori-mie53-ruro package is an npm package that has been linked to malicious activities aimed at inflating developer reputation scores through autopublishing scripts.

This vulnerability can lead to the introduction of untrusted packages in your project, potentially compromising its security and integrity.

You should remove the qori-mie53-ruro package from your project and monitor your dependencies for any instances of this package.

Yes, you can use tools like Vulert, which monitors and alerts for open-source vulnerabilities in real-time using your package-lock.json file.

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

How To Fix

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

npm uninstall qori-mie53-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