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

rita-8 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-164955: Malicious code in rita-8 (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 Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

rita-8 is an npm package that is part of the tea.xyz token reward campaign. It is designed to facilitate the generation and publication of derivative packages. However, it has been compromised, leading to significant security risks for developers who use it. The package is intended to enhance developer reputation through token rewards but has been exploited to publish malicious code.

Vulnerability Detail

The vulnerability in rita-8 originates from its association with the tea.xyz token reward campaign, which has been identified as a source of malicious packages flooding the npm registry. The malicious payload alters the package.json file by removing private flags, changing version numbers, and generating random package names. This behavior can lead to the pollution of the npm registry and compromise the integrity of applications relying on these packages.

How To Fix

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

npm uninstall rita-8

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, avoid using rita-8 and any packages that depend on it. Regularly monitor your package dependencies for any updates or vulnerabilities. You can also use tools like Vulert to check if your application is affected by this vulnerability without needing to access the code or installation.

Conclusion

The rita-8 package poses a significant security risk due to its malicious code injection vulnerability. Developers are advised to uninstall the package and monitor their dependencies closely. Utilizing tools like Vulert can help in identifying and mitigating such vulnerabilities effectively.

See every vulnerability recorded for rita-8 →

Share this vulnerability

FAQ

rita-8 is an npm package that is part of a token reward campaign aimed at enhancing developer reputation through automated package publication.

The vulnerability allows malicious code to be injected into your application, potentially compromising its security and integrity.

You should uninstall rita-8 immediately and check for any dependencies that may rely on it.

Yes, you can use Vulert to monitor your project for open-source vulnerabilities in real-time using your package-lock.json file.

You can use the Vulert playground at Vulert Scanner to check if your application is affected without any signup.

How To Fix

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

npm uninstall rita-8

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