Malicious Code Injection in rita-13 Package: npm Vulnerability Overview

rita-13 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-164882: Malicious code in rita-13 (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-13 package is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. It is designed to facilitate various functionalities within the npm registry. However, this package has been identified as malicious, containing scripts that manipulate its own package.json file and generate derivative packages with randomized names, ultimately aiming to inflate developer reputation scores for token rewards.

Vulnerability Detail

The vulnerability in the rita-13 package stems from its inclusion in a malicious campaign that floods the npm registry with derivative packages. The malicious code modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior not only compromises the integrity of the npm registry but also poses risks to developers who may unknowingly use these compromised packages, leading to potential security breaches and reputational damage.

How To Fix

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

npm uninstall rita-13

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 manually remove the rita-13 package from your project by executing the following command: npm uninstall rita-13. Additionally, consider using alternative packages that do not exhibit malicious behavior.

Conclusion

The rita-13 package has been identified as malicious, posing significant risks to developers and the integrity of the npm registry. It is crucial to remove this package from your projects 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 rita-13 →

Share this vulnerability

FAQ

The rita-13 package is an npm package associated with the tea.xyz token reward campaign, designed to facilitate various functionalities but has been identified as malicious.

The vulnerability can compromise your project's integrity by introducing malicious code that modifies package files and generates unwanted packages, potentially leading to security risks.

You can use Vulert, a tool that monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check if your application is affected without any signup.

If you have installed rita-13, it is recommended to uninstall it immediately using the command: npm uninstall rita-13 and look for alternative packages.

Currently, there is no patch available for the rita-13 package. It is essential to monitor the npm registry for any updates or patches that may address this vulnerability.

How To Fix

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

npm uninstall rita-13

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