Malicious Code Injection in polymedr-minadus-buie: A Threat to npm Packages

polymedr-minadus-buie Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-164414: Malicious code in polymedr-minadus-buie (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 package 'polymedr-minadus-buie' is part of the npm ecosystem, which is widely used for JavaScript package management. This package is associated with the tea.xyz token reward campaign, which has been linked to a series of malicious activities aimed at inflating developer reputation scores. The package's functionality is compromised by the presence of malicious scripts that automate the generation and publication of derivative packages, leading to potential security risks for users and developers alike.

Vulnerability Detail

The vulnerability in 'polymedr-minadus-buie' originates from its design to include autopublish scripts that modify the package.json file. These scripts remove private flags, alter version numbers, and generate random package names, which can lead to the pollution of the npm registry. The ramifications include the potential for developers to unknowingly install compromised packages, which can introduce further vulnerabilities or malicious behavior into their applications.

How To Fix

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

npm uninstall polymedr-minadus-buie

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 'polymedr-minadus-buie' package until a secure version is released. Additionally, consider using a tool like Vulert to monitor your package-lock.json for vulnerabilities in real-time. You can check if your application is affected by this vulnerability using the Vulert playground at https://vulert.com/scanner without any signup.

Conclusion

The 'polymedr-minadus-buie' package poses a significant risk due to its malicious code that alters package metadata and publishes unauthorized derivatives. It is essential for developers to stay informed about such vulnerabilities and take proactive measures to secure their applications by updating or removing affected packages.

See every vulnerability recorded for polymedr-minadus-buie →

Share this vulnerability

FAQ

The main issue is the presence of malicious code that modifies package.json and publishes derivative packages, which can lead to security risks.

You can use the Vulert playground at Vulert Scanner to check if your application is affected without needing to sign up.

If you have installed the 'polymedr-minadus-buie' package, it is recommended to update it to the latest patched version or remove it from your project.

Yes, the malicious code can lead to the installation of compromised packages, which may introduce further vulnerabilities into applications.

Vulert monitors your package-lock.json file to alert you in real-time about open-source vulnerabilities, helping you maintain the security of your software.

How To Fix

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

npm uninstall polymedr-minadus-buie

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