Malicious Code Injection in rita-10 Package: A Threat to npm Users

rita-10 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-164879: Malicious code in rita-10 (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 rita-10 package is part of the npm ecosystem, primarily used for various JavaScript applications. It is designed to facilitate development by providing reusable code components. However, it has been identified as part of a malicious campaign that floods the npm registry with harmful packages, undermining the integrity of the ecosystem.

Vulnerability Detail

The vulnerability in the rita-10 package stems from its association with the tea.xyz token reward campaign. This package contains malicious scripts that modify the package.json file, removing private flags and altering version numbers. It generates random package names, often themed around Indonesian culture, and continuously republishes these variants to manipulate developer reputation scores and pollute the npm registry. This poses significant risks, including the potential for code injection, dependency confusion, and the spread of malicious software.

How To Fix

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

npm uninstall rita-10

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 measure, you can avoid using the rita-10 package and replace it with a trusted alternative. Additionally, regularly audit your dependencies using tools like npm audit to identify and mitigate vulnerabilities.

Conclusion

The rita-10 package poses a significant security risk due to its malicious code designed to manipulate the npm registry. It is essential for developers to be vigilant, remove compromised packages, and utilize tools like Vulert to monitor their projects for vulnerabilities.

See every vulnerability recorded for rita-10 →

Share this vulnerability

FAQ

The rita-10 package is a JavaScript library available on npm, used for various development purposes. However, it has been compromised and is associated with malicious activities.

The vulnerability can lead to unauthorized code execution, dependency confusion, and the introduction of malicious software into your application, compromising its security.

If you have installed rita-10, it is crucial to remove it immediately and check for any other affected packages in your project.

You can use tools like 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.

Yes, consider using other reputable packages that offer similar functionality without the associated risks of the rita-10 package.

How To Fix

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

npm uninstall rita-10

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