Malicious Code Injection in polymeria-nuyio: A Threat to npm Packages

polymeria-nuyio Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-164502: Malicious code in polymeria-nuyio (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

polymeria-nuyio is an npm package that is part of the tea.xyz token reward campaign. It is designed to facilitate the distribution of token rewards through various npm packages. However, this package has been identified as malicious, containing scripts that automatically generate and publish derivative packages with altered metadata, aimed at inflating developer reputation scores.

Vulnerability Detail

The vulnerability in polymeria-nuyio stems from its malicious payload, which modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior leads to the continuous republishing of variants that pollute the npm registry, potentially compromising the integrity of the ecosystem and affecting developers relying on legitimate packages.

How To Fix

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

npm uninstall polymeria-nuyio

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 polymeria-nuyio package and consider using alternative packages that provide similar functionality without the associated risks.

Conclusion

The polymeria-nuyio package poses a significant threat due to its malicious code that alters package metadata and floods the npm registry with derivative packages. It is essential to remove this package and monitor your dependencies for vulnerabilities using tools like Vulert to maintain the integrity of your software projects.

See every vulnerability recorded for polymeria-nuyio →

Share this vulnerability

FAQ

The vulnerability involves malicious code that modifies package metadata and repackages it, leading to potential pollution of the npm registry.

You can use Vulert to monitor and alert for open-source vulnerabilities in your software. Check your application against the vulnerability using the Vulert playground at Vulert Scanner.

Immediately uninstall the package using 'npm uninstall polymeria-nuyio' and check for any other affected packages.

Yes, consider using other npm packages that provide similar functionalities without the malicious behavior. Research and verify their integrity before use.

Vulert uses your package-lock.json to monitor and alert you in real-time for open-source vulnerabilities, ensuring your application remains secure.

How To Fix

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

npm uninstall polymeria-nuyio

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