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

rita-25 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-164895: Malicious code in rita-25 (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 rita-25 package is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to facilitate token rewards through various automated scripts. However, it has been compromised to include malicious code that alters package metadata and floods the npm registry with derivative packages, potentially harming developers and users alike.

Vulnerability Detail

The vulnerability in the rita-25 package originates from its association with a malicious campaign that aims to inflate developer reputation scores for token rewards. The malicious code modifies the package.json file by removing private flags, changing version numbers, and generating random package names. This behavior leads to the continuous republishing of these variants, polluting the npm registry and potentially compromising the integrity of other packages.

How To Fix

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

npm uninstall rita-25

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 avoid using the rita-25 package and monitor your dependencies for any unauthorized changes. Regularly audit your npm packages using the command 'npm audit' to identify any vulnerabilities.

Conclusion

The rita-25 package poses a significant risk due to its malicious code that alters package metadata and floods the npm registry. It is crucial for developers to remove this package from their projects and monitor their dependencies for any vulnerabilities. Utilizing tools like Vulert can help maintain the security of your applications.

See every vulnerability recorded for rita-25 →

Share this vulnerability

FAQ

The rita-25 package is an npm package associated with the tea.xyz token reward campaign, designed to automate the generation of derivative packages.

The vulnerability can lead to the pollution of the npm registry and may compromise the integrity of your project's dependencies, potentially introducing malicious code.

If you have installed rita-25, you should uninstall it immediately using 'npm uninstall rita-25' and audit your project for any other vulnerabilities.

You can use tools like Vulert, which monitors and alerts you in real-time for open-source vulnerabilities using just your package-lock.json file.

Yes, 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 rita-25

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