Malicious Code Injection in yanti-gembus57-ruro Package

yanti-gembus57-ruro Updated 18 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-111167: Malicious code in yanti-gembus57-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 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 yanti-gembus57-ruro package is part of the npm ecosystem, often used for various JavaScript applications. This package is associated with the tea.xyz token reward campaign, which has been known to flood the npm registry with numerous derivative packages. These packages typically include scripts that automatically generate and publish new packages, potentially compromising the integrity of the npm ecosystem.

Vulnerability Detail

The vulnerability in the yanti-gembus57-ruro package stems from its malicious payload, which modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior is designed to inflate developer reputation scores for token rewards, leading to pollution of the npm registry with potentially harmful variants. The origin of this issue is linked to the broader campaign that exploits npm's publishing mechanisms, posing risks to developers and users relying on the integrity of the npm ecosystem.

How To Fix

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

npm uninstall yanti-gembus57-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 workaround, you can avoid using the yanti-gembus57-ruro package altogether. If it is already included in your project, consider removing it and replacing it with a trusted alternative. Additionally, regularly audit your package dependencies using tools like npm audit to identify and address vulnerabilities.

Conclusion

The yanti-gembus57-ruro package poses a significant risk due to its malicious behavior, which can compromise the integrity of applications relying on npm packages. It is essential to remove this package and monitor your dependencies for vulnerabilities to maintain a secure development environment.

See every vulnerability recorded for yanti-gembus57-ruro →

Share this vulnerability

FAQ

The yanti-gembus57-ruro package is an npm package associated with a token reward campaign, known for flooding the npm registry with derivative packages.

This vulnerability can compromise the integrity of your application by introducing malicious code that alters package configurations and publishes harmful variants.

If you have installed the yanti-gembus57-ruro package, it is crucial to remove it from your project and replace it with a trusted alternative.

Yes, you can use tools like Vulert, which monitors your package-lock.json file to alert you in real-time for open-source vulnerabilities.

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

How To Fix

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

npm uninstall yanti-gembus57-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