Malicious Code Injection in rita-19 Package: A Threat to npm Ecosystem

rita-19 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-164888: Malicious code in rita-19 (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 rita-19 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 various malicious activities. The primary function of rita-19 is to facilitate the distribution of JavaScript code, but it has been compromised to include harmful scripts that manipulate package metadata and inflate developer reputation scores.

Vulnerability Detail

The vulnerability in the rita-19 package originates from its association with 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, thereby polluting the npm registry. This can lead to significant security risks, including the potential for unauthorized access to sensitive data and the compromise of other packages relying on rita-19.

How To Fix

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

npm uninstall rita-19

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 rita-19 package from your project by executing the command: npm uninstall rita-19. This will prevent the execution of any malicious code until a secure version is available.

Conclusion

The rita-19 package poses a significant security risk due to its malicious code that alters package metadata and floods the npm registry. It is crucial for developers to update or remove this package to protect their applications from potential threats. Utilizing tools like Vulert can help monitor and alert for such vulnerabilities in real-time.

See every vulnerability recorded for rita-19 →

Share this vulnerability

FAQ

The rita-19 package is a JavaScript package in the npm ecosystem that has been compromised to include malicious code.

The malicious code modifies package metadata, potentially leading to unauthorized access and the pollution of the npm registry.

You should uninstall the package immediately and check for any updates or patches that may address the vulnerability.

Yes, you can use Vulert, which monitors your package-lock.json file for vulnerabilities in real-time without requiring code access or installation.

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

How To Fix

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

npm uninstall rita-19

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