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

rita-54 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-164927: Malicious code in rita-54 (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-54 package is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to facilitate the automatic generation and publication of derivative packages, which are often used to inflate developer reputation scores for token rewards. However, its malicious nature poses significant risks to developers and users alike.

Vulnerability Detail

The vulnerability in rita-54 originates from its inclusion in a campaign that floods the npm registry with malicious packages. The package contains scripts that modify the package.json file to remove private flags, alter version numbers, and generate random package names. This behavior not only pollutes the npm registry but also compromises the integrity of the packages and can lead to further exploitation by malicious actors.

How To Fix

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

npm uninstall rita-54

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-54 package altogether and monitor your dependencies for any malicious activity. Additionally, consider using tools like Vulert to monitor your package-lock.json for vulnerabilities in real-time.

Conclusion

The rita-54 package poses a significant threat due to its malicious code designed to manipulate the npm registry. It is crucial for developers to remove this package and monitor their dependencies closely. Utilizing tools like Vulert can enhance your security posture against such vulnerabilities.

See every vulnerability recorded for rita-54 →

Share this vulnerability

FAQ

rita-54 is an npm package that is part of a token reward campaign, designed to generate and publish derivative packages automatically.

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

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

You should uninstall the rita-54 package immediately using 'npm uninstall rita-54' and monitor your project for any unusual behavior.

Yes, Vulert provides a service that monitors your package-lock.json for open-source vulnerabilities in real-time, alerting you to any issues.

How To Fix

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

npm uninstall rita-54

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