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

rita-26 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-164896: Malicious code in rita-26 (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

rita-26 is an npm package that is part of the tea.xyz token reward campaign. It is designed to facilitate the distribution of token rewards through various npm packages. However, it has been identified as a malicious package that employs scripts to manipulate its own metadata and generate numerous derivative packages, thereby inflating developer reputation scores.

Vulnerability Detail

The vulnerability in rita-26 stems from its inclusion in a campaign that floods the npm registry with malicious packages. The malicious code modifies the package.json file to remove private flags, alters version numbers, and generates random package names, which leads to the pollution of the npm registry. This can result in developers inadvertently using compromised packages, exposing their applications to security risks.

How To Fix

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

npm uninstall rita-26

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 monitor your dependencies using tools like Vulert, which can alert you to vulnerabilities in your open-source packages. You can also use the Vulert playground at https://vulert.com/scanner to check if your application is affected by this vulnerability without requiring any signup.

Conclusion

The rita-26 package poses a significant threat to npm users due to its malicious code designed to manipulate package metadata and pollute the npm registry. It is essential to remove this package from your projects and utilize tools like Vulert to monitor for vulnerabilities in your dependencies.

See every vulnerability recorded for rita-26 →

Share this vulnerability

FAQ

rita-26 is an npm package associated with the tea.xyz token reward campaign, designed to distribute token rewards through npm.

The vulnerability can lead to the inclusion of malicious code in your application, potentially compromising its security and integrity.

You should uninstall the rita-26 package immediately using the command npm uninstall rita-26.

While many npm packages are safe, it is crucial to monitor your dependencies and regularly check for vulnerabilities using tools like Vulert.

You can use Vulert to monitor your package-lock.json file for vulnerabilities in real-time without needing to access the code or installation.

How To Fix

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

npm uninstall rita-26

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