Malicious Code Injection in maya-getas65-ruro: A Threat to npm Users

maya-getas65-ruro Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-105685: Malicious code in maya-getas65-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 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 package 'maya-getas65-ruro' 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 identified as containing malicious code that compromises the integrity of the npm registry.

Vulnerability Detail

The vulnerability in 'maya-getas65-ruro' originates from its malicious payload, which modifies the package.json file to remove private flags and alters version numbers. It generates random package names, primarily themed around Indonesian culture, and continuously republishes these variants to pollute the npm registry. This behavior can lead to security risks, including the potential for unauthorized access to sensitive data and the degradation of the npm ecosystem's reliability.

How To Fix

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

npm uninstall maya-getas65-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 prevent the installation of this package by using npm's package-lock.json to monitor dependencies. Additionally, consider using tools like Vulert to check for vulnerabilities in your project. You can access Vulert's playground at https://vulert.com/scanner to analyze your application without needing to sign up.

Conclusion

The 'maya-getas65-ruro' package poses a significant risk due to its malicious behavior, which can compromise the npm registry and affect developers' projects. It is crucial to take immediate action by removing the package and utilizing tools like Vulert to monitor for vulnerabilities in your software.

See every vulnerability recorded for maya-getas65-ruro →

Share this vulnerability

FAQ

The main issue is that it contains malicious code that modifies package.json files and republishes variants to the npm registry, compromising its integrity.

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

If you have installed this package, it is advisable to remove it immediately and check for any other dependencies that may be affected.

Yes, tools like Vulert can help monitor and alert you in real-time for open-source vulnerabilities in your software.

To prevent similar vulnerabilities, regularly audit your dependencies, use trusted sources for packages, and utilize tools that monitor for vulnerabilities.

How To Fix

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

npm uninstall maya-getas65-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