Malicious Code Detected in maya-liwet49-ruro: A Threat to npm Ecosystem

maya-liwet49-ruro Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-105698: Malicious code in maya-liwet49-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 Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

The package 'maya-liwet49-ruro' is part of a series of malicious npm packages linked to the tea.xyz token reward campaign. These packages are designed to manipulate the npm registry by creating and publishing numerous derivative packages with randomized names, thereby inflating developer reputation scores for token rewards. This behavior poses a significant risk to the integrity of the npm ecosystem.

Vulnerability Detail

The vulnerability in 'maya-liwet49-ruro' originates from its malicious code that modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This allows the package to continuously republish variants, polluting the npm registry and potentially leading to security risks for developers who inadvertently use these packages. The malicious payload is part of a broader strategy to exploit the npm ecosystem for token rewards.

How To Fix

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

npm uninstall maya-liwet49-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-liwet49-ruro' package and monitor your project's dependencies for any malicious packages. You can also utilize tools like Vulert to monitor your package-lock.json file for vulnerabilities. To check if your application is affected by this vulnerability, visit the Vulert playground at https://vulert.com/scanner without needing to sign up.

Conclusion

The 'maya-liwet49-ruro' package poses a significant threat to the npm ecosystem due to its malicious behavior. It is crucial for developers to be vigilant about the packages they use and to take immediate action to remove any affected packages. Utilizing tools like Vulert can help in monitoring for vulnerabilities effectively.

See every vulnerability recorded for maya-liwet49-ruro →

Share this vulnerability

FAQ

The 'maya-liwet49-ruro' package is a malicious npm package associated with a token reward campaign that aims to manipulate the npm registry.

If your project uses 'maya-liwet49-ruro', it may inadvertently contribute to the pollution of the npm registry and expose your project to security risks.

You should uninstall the package immediately using 'npm uninstall maya-liwet49-ruro' and check for any dependencies that may be affected.

Yes, regularly monitor your dependencies using tools like Vulert and stay updated on known vulnerabilities in the npm ecosystem.

Yes, you can use the Vulert playground at Vulert Scanner to check for vulnerabilities in your application without needing to sign up.

How To Fix

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

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