Malicious Code Injection in yanti-jus43-ruro: A Threat to npm Ecosystem

yanti-jus43-ruro Updated 18 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-111174: Malicious code in yanti-jus43-ruro (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 Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The package yanti-jus43-ruro is part of a series of npm packages that emerged during the tea.xyz token reward campaign. These packages are designed to manipulate the npm registry by automatically generating and publishing derivative packages with randomized names. This behavior is intended to inflate developer reputation scores for token rewards, posing a significant risk to the integrity of the npm ecosystem.

Vulnerability Detail

The vulnerability in yanti-jus43-ruro stems from its malicious payload, which modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This results in the continuous republishing of variants, which pollutes the npm registry and can lead to confusion and potential exploitation by malicious actors. The origin of this vulnerability is linked to the broader tea.xyz token reward campaign, which has been identified as a source of numerous malicious packages.

How To Fix

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

npm uninstall yanti-jus43-ruro

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 remove the yanti-jus43-ruro package from your project by executing: npm uninstall yanti-jus43-ruro. This will prevent any malicious code from executing until a fix is applied.

Conclusion

The yanti-jus43-ruro package poses a significant threat to the npm ecosystem due to its malicious behavior. It is crucial for developers to take immediate action to remove this package and monitor their projects for vulnerabilities. Utilizing tools like Vulert can help maintain the integrity of your software.

See every vulnerability recorded for yanti-jus43-ruro →

Share this vulnerability

FAQ

yanti-jus43-ruro is an npm package that has been identified as part of a malicious campaign to manipulate the npm registry.

The vulnerability can lead to the pollution of the npm registry and may expose your project to further security risks if malicious packages are inadvertently used.

You should uninstall the package immediately and monitor your project for any unauthorized changes using tools like Vulert.

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

Vulert is a tool that monitors and alerts in real-time for open-source vulnerabilities in your software using just the package-lock.json file.

How To Fix

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

npm uninstall yanti-jus43-ruro

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