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

rita-47 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-164919: Malicious code in rita-47 (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-47 package 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, this package has been identified as part of a malicious campaign that aims to exploit the npm registry by automatically generating and publishing derivative packages with altered metadata. This behavior not only undermines developer reputation but also poses a significant risk to the integrity of the npm ecosystem.

Vulnerability Detail

The vulnerability in the rita-47 package originates from its association with the tea.xyz token reward campaign. This package contains malicious scripts that modify the package.json file by removing private flags, changing version numbers, and generating random package names. The continuous republishing of these variants pollutes the npm registry, making it difficult for developers to trust legitimate packages. The ramifications include potential security risks for applications relying on affected packages and a degradation of the overall npm ecosystem's reliability.

How To Fix

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

npm uninstall rita-47

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-47 package and replace it with an alternative package that provides similar functionality without the associated risks. Always verify the integrity of packages before installation.

Conclusion

The rita-47 package poses a significant threat to the npm ecosystem due to its malicious behavior of modifying package metadata and republishing variants. It is crucial for developers to be vigilant and remove any instances of this package from their projects. Utilizing tools like Vulert can help in monitoring and identifying vulnerabilities in real-time.

See every vulnerability recorded for rita-47 →

Share this vulnerability

FAQ

The rita-47 package is a JavaScript package in the npm ecosystem that has been identified as malicious, designed to exploit the npm registry.

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

You should uninstall the rita-47 package immediately and check your dependencies for any other affected packages.

Yes, tools like Vulert can monitor your package-lock.json for vulnerabilities in real-time without requiring code access or installation.

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

How To Fix

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

npm uninstall rita-47

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