Malicious Code Injection in maya-kue75-miaww Package - npm Vulnerability

maya-kue75-miaww Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-88359: Malicious code in maya-kue75-miaww (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 maya-kue75-miaww package is part of the npm ecosystem, often utilized in JavaScript applications for various functionalities. However, it has been identified as part of a malicious campaign that floods the npm registry with derivative packages. These packages are designed to manipulate developer reputation scores through automated publishing scripts, which can lead to significant security risks.

Vulnerability Detail

The vulnerability in the maya-kue75-miaww package stems from its involvement in a token reward campaign that generates and publishes numerous derivative packages with altered metadata. This malicious behavior includes modifying the package.json file to remove private flags, changing version numbers, and creating random package names. The continuous republishing of these variants can pollute the npm registry, making it difficult for developers to trust legitimate packages and potentially leading to the installation of compromised software.

How To Fix

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

npm uninstall maya-kue75-miaww

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, avoid using the maya-kue75-miaww package and consider alternative packages that provide similar functionality without the associated risks. Additionally, you can monitor your project for vulnerabilities using tools like Vulert, which can alert you to open-source vulnerabilities in real-time.

Conclusion

The maya-kue75-miaww package poses a significant security risk due to its involvement in a malicious campaign that alters package metadata and floods the npm registry. It is essential to uninstall this package and monitor your projects for vulnerabilities to maintain a secure development environment.

See every vulnerability recorded for maya-kue75-miaww →

Share this vulnerability

FAQ

The maya-kue75-miaww package is an npm package that has been identified as part of a malicious campaign to inflate developer reputation scores through automated publishing.

This vulnerability can lead to the installation of compromised packages, potentially exposing your application to security risks and making it difficult to trust the integrity of the npm registry.

You should uninstall the maya-kue75-miaww package immediately using the command npm uninstall maya-kue75-miaww and monitor your project for any further vulnerabilities.

Yes, you can use Vulert, which monitors your package-lock.json file to alert you in real-time for open-source vulnerabilities without requiring code access or installation.

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

How To Fix

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

npm uninstall maya-kue75-miaww

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