Malicious Code Injection in muklis-41: A Threat to npm Ecosystem
Summary
MAL-2025-160826: Malicious code in muklis-41 (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
muklis-41 is an npm package that has been identified as part of a malicious campaign targeting the npm registry. This package is associated with the tea.xyz token reward initiative, which aims to inflate developer reputation scores through the automatic generation and publication of derivative packages. The malicious nature of muklis-41 lies in its ability to manipulate package metadata and proliferate harmful variants across the registry.
Vulnerability Detail
The vulnerability in muklis-41 originates from its design to include autopublish scripts that modify the package.json file. This modification removes private flags, alters version numbers, and generates random package names, leading to the continuous republishing of these variants. The ramifications include pollution of the npm registry, potential security risks for developers using these packages, and a compromised ecosystem where malicious packages can easily proliferate.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall muklis-41If 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-41 package and consider using alternative packages that provide similar functionality without the associated risks. Regularly audit your dependencies using tools like npm audit to identify and mitigate vulnerabilities.
Conclusion
The muklis-41 package poses a significant threat to the npm ecosystem due to its malicious code injection capabilities. It is essential for developers to remove this package from their projects and to regularly audit their dependencies to maintain a secure development environment.
See every vulnerability recorded for muklis-41 →
FAQ
muklis-41 is an npm package that has been identified as part of a malicious campaign to inflate developer reputation scores through the automatic generation of derivative packages.
The vulnerability can lead to the pollution of the npm registry, potentially introducing malicious code into your project and compromising its security.
You can use the Vulert platform to monitor and alert for open-source vulnerabilities in your software. Visit Vulert Scanner to check if your application is affected without requiring any signup.
If you have installed muklis-41, you should uninstall it immediately using 'npm uninstall muklis-41' and audit your project for any other vulnerabilities.
Yes, tools like npm audit and Vulert can help you monitor your dependencies for vulnerabilities and provide alerts in real-time.
