Malicious Code Injection in munir-butya-mziun: A Threat to npm Packages
Summary
MAL-2025-160882: Malicious code in munir-butya-mziun (npm). Affected versions are not published. No fix is published. How to fix ↓
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.
No signup required · Results in about 60 seconds
Background
The package 'munir-butya-mziun' is part of the npm ecosystem, which is widely used for JavaScript package management. It is designed to facilitate the development and sharing of code among developers. However, this package has been identified as part of a malicious campaign that aims to exploit the npm registry by flooding it with derivative packages that can inflate developer reputation scores for token rewards. This vulnerability poses a significant risk to developers and the integrity of the npm ecosystem.
Vulnerability Detail
The vulnerability in 'munir-butya-mziun' originates from its association with the tea.xyz token reward campaign. The package contains malicious scripts that modify the package.json file by removing private flags, altering version numbers, and generating random package names. This behavior leads to the continuous republishing of variants, polluting the npm registry and potentially compromising the security of applications that rely on this package. The malicious payload can also lead to unauthorized access to sensitive data and disrupt the normal functioning of dependent applications.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall munir-butya-mziunIf 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 the malicious package by using npm's package-lock.json to lock your dependencies. Ensure that your project does not include 'munir-butya-mziun' in its dependencies. You can also use the following command to audit your project for vulnerabilities: 'npm audit'.
Conclusion
The munir-butya-mziun package poses a significant security risk due to its malicious code designed to exploit the npm registry. Developers should take immediate action to remove the package and monitor their projects for vulnerabilities. Utilizing tools like Vulert can help maintain the integrity of your applications and protect against future threats.
See every vulnerability recorded for munir-butya-mziun →
FAQ
The main risk is that it contains malicious code that can alter your project's package.json file, potentially leading to security vulnerabilities and unauthorized access to sensitive data.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. By checking your package-lock.json file, you can identify if your application is affected. Visit the Vulert playground at Vulert Scanner for a quick assessment.
If you have installed the package, you should immediately uninstall it using 'npm uninstall munir-butya-mziun' and check your package-lock.json for any lingering references.
Currently, there is no specific patch for the munir-butya-mziun package. The best course of action is to uninstall the package and monitor for any updates from the package maintainers.
To prevent similar vulnerabilities, regularly audit your dependencies using 'npm audit', keep your packages updated, and utilize tools like Vulert to monitor for vulnerabilities in real-time.
