Malicious Code Injection in made-vs-munchen Package: npm Vulnerability Summary
Summary
MAL-2025-158996: Malicious code in made-vs-munchen (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 made-vs-munchen package is part of the npm ecosystem, typically used for various JavaScript applications. This package has been identified as part of a malicious campaign that floods the npm registry with derivative packages. The malicious nature of this package lies in its ability to modify package metadata and republish variants, which can lead to significant security risks for developers and their applications.
Vulnerability Detail
The vulnerability originates from the made-vs-munchen package being associated with the tea.xyz token reward campaign. This campaign employs malicious scripts that alter the package.json file by removing private flags, changing version numbers, and generating random package names. The continuous republishing of these variants can pollute the npm registry, making it difficult for developers to trust the integrity of packages. The ramifications include potential exposure to malicious code, compromised application security, and inflated developer reputation scores through deceptive practices.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall made-vs-munchenIf 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 made-vs-munchen package and look for alternative packages that provide similar functionality without the associated risks. Additionally, consider using tools like Vulert to monitor your package-lock.json for vulnerabilities. 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 made-vs-munchen package poses a significant security risk due to its malicious nature. Developers should take immediate action to remove this package and monitor their applications for vulnerabilities. Utilizing tools like Vulert can aid in maintaining the security of your software.
See every vulnerability recorded for made-vs-munchen →
FAQ
The made-vs-munchen package is an npm package that has been identified as part of a malicious campaign targeting the npm registry.
This vulnerability can lead to the injection of malicious code into your application, compromising its security and integrity.
You should uninstall the made-vs-munchen package immediately and check for any dependencies that may be affected.
Yes, tools like Vulert can help monitor your package-lock.json for vulnerabilities in real-time.
You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.
