Malicious Code Injection in maya-gepuk82-ruro Package

maya-gepuk82-ruro Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-105684: Malicious code in maya-gepuk82-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 maya-gepuk82-ruro package is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to facilitate the automatic generation and publication of derivative packages, which can inflate developer reputation scores for token rewards. However, it has been compromised to include malicious code that modifies package metadata.

Vulnerability Detail

The vulnerability stems from the presence of malicious code within the maya-gepuk82-ruro package. This code is designed to alter the package.json file by removing private flags, changing version numbers, and generating random package names. The malicious payload continuously republishes these variants, leading to pollution of the npm registry and potential exploitation of developers who unknowingly use these packages. The origin of this issue is linked to the tea.xyz token reward campaign, which has flooded the npm registry with such malicious packages.

How To Fix

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

npm uninstall maya-gepuk82-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 measure, avoid using the maya-gepuk82-ruro package and consider using alternative packages that provide similar functionality without the associated risks. Additionally, you can use the following command to check for vulnerabilities in your project: npm audit.

Conclusion

The maya-gepuk82-ruro package has been identified as containing malicious code that poses a significant risk to developers using it. It is essential to remove this package from your projects and monitor for any similar vulnerabilities in the future. Utilizing tools like Vulert can help maintain the security of your software.

See every vulnerability recorded for maya-gepuk82-ruro →

Share this vulnerability

FAQ

The maya-gepuk82-ruro package is an npm package associated with the tea.xyz token reward campaign, designed to automate the generation and publication of derivative packages.

The malicious code modifies your package.json file, potentially leading to security risks and pollution of the npm registry with unwanted packages.

Yes, you can use tools like Vulert to monitor your project for vulnerabilities. Vulert uses package-lock.json to alert you in real-time for open-source vulnerabilities.

If you have installed the maya-gepuk82-ruro package, you should uninstall it immediately using the command npm uninstall maya-gepuk82-ruro.

Yes, 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 maya-gepuk82-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