Malicious Code Injection in polymera-manuyat-ped Package

polymera-manuyat-ped Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-164481: Malicious code in polymera-manuyat-ped (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 Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The polymera-manuyat-ped package is part of the npm ecosystem, which is widely used for JavaScript package management. This package, like many others, is intended to facilitate the development of applications by providing reusable code components. However, it has been identified as part of a malicious campaign that exploits npm's publishing capabilities, leading to significant security risks for developers and their applications.

Vulnerability Detail

The vulnerability in the polymera-manuyat-ped package stems from its association with a malicious campaign that floods the npm registry with derivative packages. This package contains scripts that automatically modify the package.json file to remove private flags, alter version numbers, and generate random package names. The malicious payload continuously republishes these variants, which can lead to reputation inflation for developers and compromise the integrity of the npm registry. The origin of this vulnerability is linked to the tea.xyz token reward campaign, which aims to manipulate npm's ecosystem for token rewards.

How To Fix

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

npm uninstall polymera-manuyat-ped

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 polymera-manuyat-ped package and replace it with a trusted alternative. Additionally, consider using tools like Vulert to monitor your package-lock.json for vulnerabilities in real-time.

Conclusion

The polymera-manuyat-ped package poses a significant security risk due to its malicious code that alters package configurations and floods the npm registry. It is crucial for developers to remove this package and monitor their dependencies for vulnerabilities to maintain the integrity of their applications.

See every vulnerability recorded for polymera-manuyat-ped →

Share this vulnerability

FAQ

The polymera-manuyat-ped package is an npm package that has been identified as part of a malicious campaign to manipulate the npm registry.

This vulnerability can compromise the integrity of your application by introducing malicious code that modifies your package configurations and potentially leads to security breaches.

You should uninstall the polymera-manuyat-ped package immediately and ensure that your project dependencies are secure and up-to-date.

Yes, you can use Vulert's playground to check if your application is affected by this vulnerability without any signup required.

Vulert is a tool that monitors and alerts for open-source vulnerabilities in your software using just package-lock.json. It provides real-time alerts for any vulnerabilities detected.

How To Fix

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

npm uninstall polymera-manuyat-ped

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