Malicious Code Injection in muklis-50: A Threat to npm Packages
Summary
MAL-2025-160836: Malicious code in muklis-50 (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 muklis-50 package is part of a series of npm packages that have been identified as part of a malicious campaign associated with the tea.xyz token reward initiative. These packages are designed to manipulate the npm registry by generating and publishing numerous derivative packages with randomized names. This behavior not only inflates developer reputation scores but also poses a significant risk to the integrity of the npm ecosystem.
Vulnerability Detail
The vulnerability in muklis-50 originates from its inclusion in a malicious package set that modifies the package.json file to remove private flags, alters version numbers, and creates random package names. This malicious payload allows the package to continuously republish variants, effectively polluting the npm registry. The ramifications include potential security risks for developers who unknowingly use these packages, as they may inadvertently integrate malicious code into their applications.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall muklis-50If 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, avoid using the muklis-50 package and consider using alternative packages that provide similar functionality without the associated risks. Additionally, regularly audit your dependencies to identify and remove any malicious packages.
Conclusion
The muklis-50 package poses a significant security risk due to its malicious code that alters package metadata and repopulates the npm registry with harmful variants. It is essential for developers to remove this package and monitor their dependencies regularly to maintain the integrity of their applications.
See every vulnerability recorded for muklis-50 →
FAQ
Muklis-50 is an npm package that has been identified as part of a malicious campaign aimed at manipulating the npm registry.
The vulnerability can lead to the introduction of malicious code into your application, potentially compromising its security and integrity.
You can use Vulert, a tool that monitors and alerts for open-source vulnerabilities in your software. Visit Vulert Scanner to check your application without requiring any signup.
If you have used muklis-50, it is crucial to uninstall the package immediately and audit your code for any potential security issues.
Yes, consider using other reputable npm packages that provide similar functionality without the associated risks of malicious behavior.
