Malicious Code Injection in rita-23 Package: npm Vulnerability Overview

rita-23 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-164893: Malicious code in rita-23 (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 rita-23 package is part of the npm ecosystem, primarily used for various JavaScript applications. It is often included in projects for its utility functions. However, it has been identified as part of a malicious campaign that aims to exploit npm's package management system. The vulnerability stems from the package's ability to modify its own metadata and republish itself under different names, which can lead to reputation inflation and potential security risks for developers and users alike.

Vulnerability Detail

The rita-23 package contains malicious code that modifies the package.json file to remove private flags and alters version numbers. It generates random package names, often themed around Indonesian culture, and continuously republishes these variants to the npm registry. This behavior can lead to the pollution of the npm ecosystem, making it difficult for developers to trust the integrity of packages. The vulnerability originates from a campaign designed to inflate developer reputation scores for token rewards, posing significant risks to users who may unknowingly install compromised packages.

How To Fix

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

npm uninstall rita-23

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 the rita-23 package in your projects. Instead, consider using alternative packages that provide similar functionality without the associated risks. Always ensure to check the package's reputation and reviews before installation.

Conclusion

The rita-23 package poses a significant security risk due to its malicious code that modifies package metadata and repackages itself. Developers should take immediate action to remove this package and monitor their projects for vulnerabilities. Utilizing tools like Vulert can help maintain the security of your applications.

See every vulnerability recorded for rita-23 →

Share this vulnerability

FAQ

The rita-23 package is a JavaScript library available on npm, used for various utility functions in applications.

The vulnerability can lead to the installation of malicious code that modifies your project's dependencies and can compromise security.

You should uninstall the rita-23 package immediately and check your project for any unauthorized changes.

You can use tools like Vulert, which monitors your package-lock.json for vulnerabilities in real-time without requiring code access.

Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without signing up.

How To Fix

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

npm uninstall rita-23

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