Malicious Code Injection in muklis-10: A Threat to npm Ecosystem
Summary
MAL-2025-160793: Malicious code in muklis-10 (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 'muklis-10' is part of the npm ecosystem, which is widely used for JavaScript package management. It is associated with the tea.xyz token reward campaign, which has been known to flood the npm registry with malicious packages. These packages often contain scripts designed to manipulate package metadata and inflate developer reputation scores, posing significant risks to developers and users alike.
Vulnerability Detail
The vulnerability in 'muklis-10' originates from its design to include malicious scripts that modify the package.json file. These scripts remove private flags, alter version numbers, and generate random package names, leading to the continuous republishing of variants that pollute the npm registry. This not only compromises the integrity of the npm ecosystem but also affects developers' reputations and can lead to further exploitation.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall muklis-10If 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 'muklis-10' package and replace it with a trusted alternative. Always verify the integrity of packages before installation.
Conclusion
The 'muklis-10' package poses a significant risk to the npm ecosystem due to its malicious code designed to manipulate package metadata. It is crucial for developers to remove this package and monitor their dependencies closely to maintain the integrity of their applications.
See every vulnerability recorded for muklis-10 →
FAQ
The main threat is the malicious code that modifies package metadata, leading to the pollution of the npm registry and potential exploitation of developers' reputations.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check if your application is affected without requiring any signup.
Immediately uninstall the package using 'npm uninstall muklis-10' and review your project's dependencies for any other potentially malicious packages.
Yes, consider using well-established and trusted packages that serve the same purpose as muklis-10, ensuring they are regularly maintained and reviewed.
Regularly audit your dependencies, use tools like Vulert for monitoring, and only install packages from reputable sources.
