Malicious Code Injection in muklis-56: A Threat to npm Users
Summary
MAL-2025-160842: Malicious code in muklis-56 (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-56 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 linked to numerous malicious packages flooding the npm registry. These packages are designed to manipulate developer reputation scores by automatically generating and publishing derivative packages with randomized names, ultimately compromising the integrity of the npm ecosystem.
Vulnerability Detail
The vulnerability in muklis-56 originates from its malicious payload that modifies the package.json file to remove private flags and alters version numbers. It generates random package names, often themed around Indonesian culture, and continuously republishes these variants to pollute the npm registry. This behavior not only affects the reputation of developers but also poses a risk of dependency confusion and potential exploitation of applications relying on these packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall muklis-56If 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 measure, avoid using the muklis-56 package and consider using alternative packages that provide similar functionality without the associated risks. Additionally, you can monitor your project for vulnerabilities using tools like Vulert, which can alert you to open-source vulnerabilities in real-time.
Conclusion
The muklis-56 package poses a significant threat to npm users due to its malicious behavior of modifying package metadata and republishing harmful variants. It is crucial to uninstall this package and monitor your dependencies for vulnerabilities to maintain the security of your applications.
See every vulnerability recorded for muklis-56 →
FAQ
Muklis-56 is an npm package that has been identified as part of a malicious campaign to inflate developer reputation scores through automated publishing of derivative packages.
The vulnerability can lead to dependency confusion, where your application may inadvertently rely on malicious packages, potentially compromising security and functionality.
You should uninstall the muklis-56 package immediately using 'npm uninstall muklis-56' and review your project's dependencies for any other potentially malicious packages.
Yes, regularly audit your dependencies, use tools like Vulert to monitor for vulnerabilities, and be cautious when adding new packages from the npm registry.
Vulert is a tool that monitors your package-lock.json file to alert you in real-time about open-source vulnerabilities. You can check if your application is affected by this vulnerability using the Vulert playground without any signup.
