Malicious Code Injection in polymedr-mindatas-bui: A Threat to npm Ecosystem

polymedr-mindatas-bui Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-164420: Malicious code in polymedr-mindatas-bui (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 Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

The package 'polymedr-mindatas-bui' 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 known to flood the npm registry with malicious packages. These packages often contain scripts that manipulate package metadata to inflate developer reputation scores, posing a significant risk to developers and users alike.

Vulnerability Detail

The vulnerability in 'polymedr-mindatas-bui' originates from its association with malicious scripts designed to autopublish derivative packages with randomized names. These scripts modify the package.json file to remove private flags, alter version numbers, and continuously republish variants, thereby polluting the npm registry. The ramifications include compromised developer accounts, potential data breaches, and a degraded trust in the npm ecosystem.

How To Fix

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

npm uninstall polymedr-mindatas-bui

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-mindatas-bui' package from your project by executing 'npm uninstall polymedr-mindatas-bui'. This will prevent any malicious code from executing while you assess the situation.

Conclusion

The 'polymedr-mindatas-bui' package poses a significant threat due to its malicious code that alters package metadata and floods the npm registry. It is crucial for developers to stay informed about such vulnerabilities, apply updates promptly, and utilize tools like Vulert to monitor their applications for potential risks.

See every vulnerability recorded for polymedr-mindatas-bui →

Share this vulnerability

FAQ

The vulnerability involves malicious scripts that manipulate package metadata and republish variants to the npm registry.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check your application without any signup.

Using this package can lead to compromised developer accounts, data breaches, and a loss of trust in the npm ecosystem.

Check the package repository for any updates or patches. If available, update the package using 'npm update polymedr-mindatas-bui'.

As a temporary measure, uninstall the package using 'npm uninstall polymedr-mindatas-bui' to prevent any malicious activity.

How To Fix

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

npm uninstall polymedr-mindatas-bui

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