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

rita-76 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

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

The package rita-76 is part of the npm ecosystem, which is widely used for JavaScript package management. It is designed to facilitate the development and distribution of JavaScript applications. However, rita-76 has been identified as part of a malicious campaign that exploits npm's publishing capabilities, leading to potential security risks for developers and users alike.

Vulnerability Detail

The vulnerability in rita-76 originates from its association with the tea.xyz token reward campaign, which has been flooding the npm registry with malicious packages. The package contains scripts that automatically modify package.json files to remove private flags, change version numbers, and generate random package names. This behavior can lead to the pollution of the npm registry, inflate developer reputation scores fraudulently, and potentially introduce harmful code into applications that depend on these packages.

How To Fix

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

npm uninstall rita-76

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-76 package and look for alternative packages that provide similar functionality without the associated risks. Additionally, consider implementing strict package validation and monitoring practices in your development workflow.

Conclusion

The rita-76 package poses a significant threat due to its malicious code designed to manipulate the npm registry. It is crucial for developers to be vigilant, remove affected packages, and adopt best practices to safeguard their applications from such vulnerabilities.

See every vulnerability recorded for rita-76 →

Share this vulnerability

FAQ

Rita-76 is an npm package that has been linked to a malicious campaign aimed at manipulating the npm registry and inflating developer reputation scores.

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

You should immediately remove the rita-76 package from your project and monitor your application for any signs of compromise.

Yes, tools like Vulert can help monitor and alert you in real-time for open-source vulnerabilities in your software. You can check if your application is affected by using the Vulert playground without any signup.

To prevent similar vulnerabilities, regularly audit your dependencies, use trusted sources for packages, and implement security best practices in your development process.

How To Fix

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

npm uninstall rita-76

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