Malicious Code Injection in ruji-20 Package: A Threat to npm Ecosystem

ruji-20 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-165245: Malicious code in ruji-20 (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 ruji-20 package is part of the npm ecosystem, which is widely used for JavaScript package management. This package, like many others, is intended to facilitate the development of applications by providing reusable code. However, it has been identified as part of a malicious campaign that aims to exploit the npm registry by flooding it with derivative packages that can inflate developer reputation scores for token rewards.

Vulnerability Detail

The vulnerability in the ruji-20 package stems from its association with the tea.xyz token reward campaign. It contains malicious scripts that modify the package.json file to remove private flags, alter version numbers, and generate random package names. This behavior leads to the continuous republishing of these variants, which pollutes the npm registry and can compromise the integrity of the ecosystem. The malicious payload can potentially allow unauthorized access to sensitive information and disrupt the normal functioning of applications relying on this package.

How To Fix

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

npm uninstall ruji-20

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, you can remove the ruji-20 package from your project to prevent any potential exploitation. You can do this by executing the command: npm uninstall ruji-20. Additionally, consider using tools like Vulert to monitor your project for vulnerabilities in real-time.

Conclusion

The ruji-20 package poses a significant threat to the npm ecosystem due to its malicious code designed to exploit the registry. It is essential for developers to take immediate action by uninstalling the package and monitoring their projects for vulnerabilities. Utilizing tools like Vulert can provide additional security and peace of mind.

See every vulnerability recorded for ruji-20 →

Share this vulnerability

FAQ

The ruji-20 package is an npm package that has been identified as part of a malicious campaign aimed at exploiting the npm registry.

The malicious code can modify your package.json file, remove private flags, and republish variants, potentially compromising your application's integrity.

You should uninstall the ruji-20 package immediately and monitor your project for vulnerabilities using tools like Vulert.

Regularly update your packages, use tools to monitor for vulnerabilities, and review the packages you include in your projects.

Vulert monitors your package-lock.json file to alert you in real-time about open-source vulnerabilities, helping you maintain a secure application.

How To Fix

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

npm uninstall ruji-20

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