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

ruji-12 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-165236: Malicious code in ruji-12 (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 Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

Background

The package 'ruji-12' is part of the npm ecosystem, which is widely used for managing JavaScript packages. It is often utilized in various applications to enhance functionality through third-party libraries. However, 'ruji-12' has been identified as part of a malicious campaign that aims to exploit the npm registry by flooding it with derivative packages. This not only affects the reputation of developers but also poses significant risks to applications relying on these packages.

Vulnerability Detail

The vulnerability in 'ruji-12' originates from its association with the tea.xyz token reward campaign, which has been known to deploy malicious scripts. These scripts, such as auto.js and autopublish.js, are designed to modify the package.json file by removing private flags, altering version numbers, and generating random package names. The continuous republishing of these variants leads to pollution of the npm registry, potentially compromising the integrity of applications that depend on these packages. The ramifications include increased security risks, potential data breaches, and a degraded developer reputation.

How To Fix

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

npm uninstall ruji-12

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, avoid using 'ruji-12' and any packages that may depend on it. Instead, look for alternative packages that provide similar functionality without the associated risks. Additionally, you can monitor your project for vulnerabilities using tools like Vulert, which can alert you to open-source vulnerabilities in real-time.

Conclusion

The 'ruji-12' package poses a significant threat to the npm ecosystem due to its malicious nature. It is essential for developers to be vigilant and remove any instances of this package from their projects. Utilizing tools like Vulert can help in monitoring and managing vulnerabilities effectively.

See every vulnerability recorded for ruji-12 →

Share this vulnerability

FAQ

'ruji-12' is an npm package that has been identified as part of a malicious campaign to exploit the npm registry.

The vulnerability can lead to the modification of your package.json file, potentially compromising your application's integrity and security.

You should uninstall 'ruji-12' immediately and look for alternative packages to avoid potential security risks.

You can use Vulert to monitor your application for open-source vulnerabilities in real-time without needing to access the code or installation.

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

Sponsored Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

How To Fix

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

npm uninstall ruji-12

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