Malicious Code Injection in polymera-manuyat-muniosps Package

polymera-manuyat-muniosps Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-164479: Malicious code in polymera-manuyat-muniosps (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 Your last release was probably never penetration tested 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-muniosps package is part of the npm ecosystem, which is widely used for JavaScript development. This package has been identified as part of a malicious campaign that aims to inflate developer reputation scores through the automatic generation and publication of derivative packages. The malicious nature of this package poses significant risks to developers and their projects.

Vulnerability Detail

The vulnerability stems from the package being involved in a token reward campaign that floods the npm registry with malicious packages. It contains scripts that modify the package.json file to remove private flags, change version numbers, and generate random package names. This behavior not only pollutes the npm registry but also compromises the integrity of projects that depend on this package, potentially leading to further exploitation.

How To Fix

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

npm uninstall polymera-manuyat-muniosps

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 polymera-manuyat-muniosps package and any of its derivatives. Additionally, consider using package-lock.json to monitor your dependencies for vulnerabilities. You can also utilize tools like Vulert to check if your application is affected by this vulnerability without requiring code access or installation.

Conclusion

The polymera-manuyat-muniosps package presents a significant security risk due to its involvement in a malicious campaign. It is essential for developers to take immediate action by removing the package and monitoring their projects for vulnerabilities. Utilizing tools like Vulert can aid in maintaining the security of your applications.

See every vulnerability recorded for polymera-manuyat-muniosps →

Share this vulnerability

FAQ

It is an npm package that has been identified as part of a malicious campaign to inflate developer reputation scores.

The vulnerability can lead to the pollution of the npm registry and compromise the integrity of your project's dependencies.

You should remove the polymera-manuyat-muniosps package from your project and monitor for any updates or patches.

Yes, you can use Vulert's playground to check for vulnerabilities in your application using package-lock.json.

Regularly monitor your dependencies, use tools like Vulert, and stay updated on security advisories for the packages you use.

How To Fix

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

npm uninstall polymera-manuyat-muniosps

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