Malicious Code Injection in maya-miemee15-pore: A Threat to npm Packages

maya-miemee15-pore Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-98130: Malicious code in maya-miemee15-pore (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 Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

Background

The package 'maya-miemee15-pore' is part of the npm ecosystem, which is widely used for JavaScript package management. It is often utilized in various applications to enhance functionality and streamline development processes. However, this package has been identified as part of a malicious campaign that aims to exploit npm's publishing mechanisms, leading to potential security risks for developers and users alike.

Vulnerability Detail

The vulnerability in 'maya-miemee15-pore' originates from its involvement in a token reward campaign that floods the npm registry with malicious packages. These packages contain scripts designed to automatically publish derivative packages with altered metadata, including the removal of private flags and the generation of random package names. This behavior not only inflates developer reputation scores but also pollutes the npm registry, making it difficult for users to find legitimate packages. The malicious payload can lead to unauthorized access, data breaches, and a compromised development environment.

How To Fix

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

npm uninstall maya-miemee15-pore

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, you can avoid using the 'maya-miemee15-pore' package and replace it with a trusted alternative. Always verify the integrity and source of packages before including them in your project.

Conclusion

The 'maya-miemee15-pore' package poses a significant security risk due to its malicious nature. Developers should take immediate action to remove this package and ensure their applications are secure. Utilizing tools like Vulert can help in monitoring for vulnerabilities and maintaining a secure development environment.

See every vulnerability recorded for maya-miemee15-pore →

Share this vulnerability

FAQ

The vulnerability can lead to the injection of malicious code, unauthorized access to your application, and pollution of the npm registry.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check your application without any signup.

You should uninstall the package immediately using 'npm uninstall maya-miemee15-pore' and review your project for any other potentially vulnerable packages.

Currently, there are no patches available for the 'maya-miemee15-pore' package. The best course of action is to remove it from your project.

Regularly audit your dependencies, use tools like Vulert for monitoring, and only install packages from trusted sources.

Sponsored Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

How To Fix

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

npm uninstall maya-miemee15-pore

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