Malicious Code Injection in polymeria-mayani: A Threat to npm Ecosystem

polymeria-mayani Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-164496: Malicious code in polymeria-mayani (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 package polymeria-mayani is part of the npm ecosystem, which is widely used for JavaScript package management. It is designed to facilitate the development and distribution of JavaScript applications. However, this package has been identified as part of a malicious campaign that aims to inflate developer reputation scores through the creation of derivative packages with randomized names. This vulnerability poses a significant risk to developers and users relying on npm for secure package management.

Vulnerability Detail

The vulnerability in polymeria-mayani originates from its involvement in the tea.xyz token reward campaign, which has been flooding the npm registry with malicious packages. These packages contain scripts that automatically modify the package.json file to remove private flags, alter version numbers, and generate random package names. The continuous republishing of these variants can lead to pollution of the npm registry, making it difficult for developers to identify legitimate packages. The ramifications include potential security risks, loss of trust in the npm ecosystem, and the possibility of malicious code execution in applications relying on these packages.

How To Fix

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

npm uninstall polymeria-mayani

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 avoid using the polymeria-mayani package and look for alternative packages that provide similar functionality without the associated risks. Always verify the integrity and reputation of packages before including them in your project.

Conclusion

The polymeria-mayani package poses a significant security risk due to its involvement in a malicious campaign that modifies package metadata and floods the npm registry. It is crucial for developers to remove this package from their projects and adopt best practices for monitoring and managing dependencies to maintain the integrity of their applications.

See every vulnerability recorded for polymeria-mayani →

Share this vulnerability

FAQ

polymeria-mayani is an npm package that has been identified as part of a malicious campaign aimed at inflating developer reputation scores through the creation of derivative packages.

The vulnerability can lead to the introduction of malicious code into your application, potentially compromising its security and integrity.

You should uninstall the package immediately using the command npm uninstall polymeria-mayani and review your project's dependencies for any other potentially malicious packages.

You can use tools like Vulert, which monitors your package-lock.json file to alert you in real-time for open-source vulnerabilities in your software.

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 polymeria-mayani

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