Malicious Code Injection in polymedarnan-munitsat-budipe Package

polymedarnan-munitsat-budipe Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-164396: Malicious code in polymedarnan-munitsat-budipe (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 polymedarnan-munitsat-budipe package is part of the npm ecosystem, often utilized in JavaScript projects for various functionalities. However, it has been identified as part of a malicious campaign that floods the npm registry with derivative packages. These packages are designed to manipulate developer reputation scores through automated publishing scripts, which can lead to a polluted registry and potential security risks for users.

Vulnerability Detail

The vulnerability stems from the package's involvement in the tea.xyz token reward campaign, which employs malicious scripts to modify the package.json file. This includes removing private flags, altering version numbers, and generating random package names. The continuous republishing of these variants can compromise the integrity of the npm registry, making it difficult for developers to trust the packages they use. The malicious payload can lead to unintended consequences, such as the inclusion of untrusted code in applications that depend on these packages.

How To Fix

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

npm uninstall polymedarnan-munitsat-budipe

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 polymedarnan-munitsat-budipe package and replace it with a trusted alternative. Regularly monitor your package dependencies for any signs of malicious activity.

Conclusion

The polymedarnan-munitsat-budipe package poses a significant security risk due to its malicious code injection. It is essential for developers to be vigilant in monitoring their dependencies and to take immediate action to remove any affected packages. Utilizing tools like Vulert can aid in maintaining the security of your projects.

See every vulnerability recorded for polymedarnan-munitsat-budipe →

Share this vulnerability

FAQ

It is an npm package that has been identified as part of a malicious campaign aimed at inflating developer reputation scores through automated publishing.

The vulnerability can lead to the inclusion of untrusted code in your application, potentially compromising its security and integrity.

You should uninstall the package immediately using npm uninstall polymedarnan-munitsat-budipe and monitor your project for any unusual behavior.

You can use tools like Vulert, which monitors your package-lock.json for open-source vulnerabilities in real-time without requiring code access or installation.

Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.

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 polymedarnan-munitsat-budipe

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