Malicious Code Injection in polymedr-minda-buipenajaran: A Threat to npm Packages

polymedr-minda-buipenajaran Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-164416: Malicious code in polymedr-minda-buipenajaran (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-minda-buipenajaran' is part of a broader campaign targeting the npm ecosystem, specifically linked to the tea.xyz token reward initiative. This package is designed to facilitate the automatic generation and publication of derivative packages, which can inflate developer reputation scores. Its functionality is compromised by malicious scripts that alter package metadata and publish harmful variants to the npm registry.

Vulnerability Detail

The vulnerability in 'polymedr-minda-buipenajaran' stems from its inclusion in a malicious campaign that utilizes scripts to modify the package.json file. This modification removes private flags, alters version numbers, and generates random package names, leading to the pollution of the npm registry. The potential ramifications include the proliferation of malicious packages that can mislead developers and compromise the integrity of the npm ecosystem. The technical aspects involve the use of autopublish scripts (auto.js, autopublish.js, etc.) that automate these harmful actions.

How To Fix

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

npm uninstall polymedr-minda-buipenajaran

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 prevent the installation of this malicious package by using npm's package-lock.json to monitor dependencies. Additionally, consider using tools like Vulert to check for vulnerabilities in your project without needing to access the code directly.

Conclusion

The 'polymedr-minda-buipenajaran' package poses a significant threat due to its malicious code that alters package metadata and publishes harmful variants. It is essential to take immediate action by uninstalling the package and monitoring your project for vulnerabilities using tools like Vulert.

See every vulnerability recorded for polymedr-minda-buipenajaran →

Share this vulnerability

FAQ

The vulnerability involves malicious code that modifies package metadata and publishes harmful variants to the npm registry.

You can use Vulert to monitor your package-lock.json for vulnerabilities in real-time without requiring code access.

Uninstall the package using 'npm uninstall polymedr-minda-buipenajaran' and check for any updates or patches.

Yes, tools like Vulert can help monitor and alert you to open-source vulnerabilities in your software.

Leaving this vulnerability unaddressed can lead to the proliferation of malicious packages, compromising the integrity of your project and potentially exposing sensitive data.

How To Fix

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

npm uninstall polymedr-minda-buipenajaran

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