Malicious Code Injection in polymedr-munisat-budipe Package

polymedr-munisat-budipe Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-164443: Malicious code in polymedr-munisat-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 polymedr-munisat-budipe package is part of the npm ecosystem, typically used for various JavaScript applications. It is associated with the tea.xyz token reward campaign, which has been linked to a series of malicious packages that flood the npm registry. These packages often contain scripts designed to manipulate package metadata and inflate developer reputation scores.

Vulnerability Detail

The vulnerability in the polymedr-munisat-budipe package stems from the presence of malicious code that modifies the package.json file. This code removes private flags, alters version numbers, and generates random package names, which leads to the continuous republishing of these variants. The origin of this vulnerability is tied to the tea.xyz token reward campaign, which aims to exploit npm's registry by creating a large number of derivative packages. The ramifications include potential pollution of the npm registry, loss of developer reputation, and exposure to further malicious activities.

How To Fix

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

npm uninstall polymedr-munisat-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 workaround, you can remove the polymedr-munisat-budipe package from your project by executing: npm uninstall polymedr-munisat-budipe. This will prevent any malicious code from executing until a safe version is available.

Conclusion

The polymedr-munisat-budipe package contains a significant vulnerability due to malicious code that alters package metadata and floods the npm registry with derivative packages. It is crucial to update or remove this package to protect your project from potential risks associated with this vulnerability.

See every vulnerability recorded for polymedr-munisat-budipe →

Share this vulnerability

FAQ

It is an npm package that has been linked to a malicious campaign aimed at inflating developer reputation scores through the creation of numerous derivative packages.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software. By analyzing your package-lock.json file, Vulert can provide real-time alerts for vulnerabilities.

The risks include the potential for your project to be associated with malicious activities, loss of reputation, and exposure to further attacks through the polluted npm registry.

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

If immediate updates are not possible, consider removing the package as a temporary measure to mitigate risks until a safe version is available.

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 polymedr-munisat-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