Malicious Code Injection in qori-lupis70-ruro Package

qori-lupis70-ruro Updated 18 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-107591: Malicious code in qori-lupis70-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 MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

The qori-lupis70-ruro package is part of the npm ecosystem and appears to be associated with the tea.xyz token reward campaign. This package is designed to automate the generation and publication of derivative packages with randomized names, which can inflate developer reputation scores for token rewards. The malicious nature of this package poses significant risks to users and the integrity of the npm registry.

Vulnerability Detail

The vulnerability in the qori-lupis70-ruro package originates from its inclusion in a campaign that floods the npm registry with malicious packages. It contains scripts that modify the package.json file to remove private flags, change version numbers, and generate random package names. This behavior leads to the continuous republishing of variants, polluting the npm registry and potentially compromising the security of applications that rely on this package.

How To Fix

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

npm uninstall qori-lupis70-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 remove the qori-lupis70-ruro package from your dependencies by running the following command: npm uninstall qori-lupis70-ruro. This will help mitigate the risks associated with the malicious code until a fix is implemented.

Conclusion

The qori-lupis70-ruro package contains malicious code that poses significant risks to users and the integrity of the npm registry. It is crucial to remove this package from your project and monitor for any updates or patches. Utilizing tools like Vulert can help you stay informed about vulnerabilities in your dependencies.

See every vulnerability recorded for qori-lupis70-ruro →

Share this vulnerability

FAQ

The qori-lupis70-ruro package is an npm package associated with a token reward campaign that automates the generation of derivative packages.

The vulnerability can lead to the pollution of the npm registry and may compromise the security of applications that depend on this package.

You should uninstall the qori-lupis70-ruro package immediately to prevent any potential security risks.

Yes, you can use 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-lupis70-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