Malicious Code Injection in munir-butya-tyu Package: A Threat to npm Ecosystem

munir-butya-tyu Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-160892: Malicious code in munir-butya-tyu (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 munir-butya-tyu package is part of the npm ecosystem, which is widely used for JavaScript package management. This package, like many others, is intended to facilitate the development and deployment of applications by providing reusable code components. However, it has been identified as part of a malicious campaign that aims to exploit the npm registry by flooding it with derivative packages that can manipulate developer reputation scores.

Vulnerability Detail

The vulnerability in the munir-butya-tyu package originates from its association with a token reward campaign that utilizes autopublish scripts. These scripts are designed to automatically generate and publish numerous derivative packages with randomized names, effectively polluting the npm registry. The malicious payload modifies the package.json file to remove private flags, alters version numbers, and continuously republishes variants, which can lead to significant security risks, including the potential for dependency confusion and the introduction of malicious code into legitimate projects.

How To Fix

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

npm uninstall munir-butya-tyu

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 munir-butya-tyu package and replace it with alternative packages that provide similar functionality without the associated risks. Always verify the integrity and reputation of packages before including them in your project.

Conclusion

The munir-butya-tyu package poses a significant threat to the npm ecosystem due to its malicious code injection capabilities. It is essential for developers to be vigilant about the packages they include in their projects and to take proactive measures to secure their applications. Regularly updating dependencies and utilizing tools like Vulert can help mitigate these risks.

See every vulnerability recorded for munir-butya-tyu →

Share this vulnerability

FAQ

The munir-butya-tyu package is a JavaScript package available on npm, which has been identified as part of a malicious campaign to manipulate the npm registry.

This vulnerability can lead to the introduction of malicious code into your project, potentially compromising its security and integrity.

If you have installed the munir-butya-tyu package, you should uninstall it immediately and review your project's dependencies for any other potentially malicious packages.

You can use Vulert, which monitors and alerts in real-time for open-source vulnerabilities using just your package-lock.json file. You can check if your application is affected by this vulnerability using the Vulert playground without any signup.

Yes, consider using other reputable packages that provide similar functionality but do not have the associated risks of malicious code.

How To Fix

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

npm uninstall munir-butya-tyu

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