Malicious Code Injection in qori-klanting100-ruro Package

qori-klanting100-ruro Updated 18 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-107579: Malicious code in qori-klanting100-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 Your last release was probably never penetration tested 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-klanting100-ruro package is part of the npm ecosystem, often used for various JavaScript applications. It is associated with the tea.xyz token reward campaign, which has been known to flood the npm registry with packages designed to manipulate developer reputation scores. This package, like others in the campaign, contains scripts that automate the generation and publication of derivative packages, making it susceptible to malicious exploitation.

Vulnerability Detail

The vulnerability in the qori-klanting100-ruro package stems from its involvement in a malicious campaign that modifies the package.json file to remove private flags and change version numbers. It generates random package names, often themed around Indonesian culture, and continuously republishes these variants, leading to pollution of the npm registry. This can result in a loss of trust in the affected packages and potential security risks for applications relying on them.

How To Fix

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

npm uninstall qori-klanting100-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 workaround, you can temporarily avoid using the qori-klanting100-ruro package by replacing it with an alternative package that provides similar functionality. Additionally, you can monitor your project for any malicious activity using tools like Vulert, which can alert you to vulnerabilities in your package-lock.json file.

Conclusion

The qori-klanting100-ruro package poses a significant security risk due to its malicious code injection vulnerability. It is crucial for developers to remove this package and monitor their applications for any signs of compromise. Utilizing tools like Vulert can provide additional security assurance.

See every vulnerability recorded for qori-klanting100-ruro →

Share this vulnerability

FAQ

It is an npm package associated with the tea.xyz token reward campaign, often used in JavaScript applications.

The vulnerability can lead to the injection of malicious code, compromising the security and integrity of your application.

You should remove the qori-klanting100-ruro package and consider using an alternative package. Additionally, monitor your project for vulnerabilities.

Yes, you can use Vulert's playground to check your application for vulnerabilities without needing to sign up.

Vulert monitors and alerts you in real-time for open-source vulnerabilities using just your package-lock.json file, helping you maintain application security.

How To Fix

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

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