Malicious Code Injection in muklis-2: A Threat to npm Ecosystem
Summary
MAL-2025-160803: Malicious code in muklis-2 (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-2 package is part of the npm ecosystem, which is widely used for JavaScript package management. This package has been identified as part of a malicious campaign that aims to exploit the npm registry by flooding it with derivative packages. The primary functionality of muklis-2 is to act as a token reward mechanism for the tea.xyz protocol, but it has been compromised to include harmful scripts that manipulate package metadata.
Vulnerability Detail
The vulnerability in muklis-2 stems from its association with a malicious campaign that modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior is designed to inflate developer reputation scores for token rewards, leading to pollution of the npm registry. The malicious payload can result in unauthorized access to sensitive data and compromise the integrity of applications relying on this package.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall muklis-2If 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-2 package altogether and look for alternative packages that provide similar functionality without the associated risks. Additionally, consider using tools like Vulert to monitor your project for vulnerabilities. You can check if your application is affected by this vulnerability using the Vulert playground at https://vulert.com/scanner.
Conclusion
The muklis-2 package poses a significant risk to the npm ecosystem due to its malicious code that alters package metadata. It is crucial for developers to remove this package and monitor their projects for vulnerabilities to maintain application security.
See every vulnerability recorded for muklis-2 →
FAQ
Muklis-2 is an npm package that has been identified as part of a malicious campaign targeting the npm ecosystem.
The vulnerability can lead to unauthorized modifications of your package.json file, potentially compromising your application's integrity and security.
You should uninstall the muklis-2 package immediately and check for any dependencies that may be affected.
Yes, you can use Vulert, which monitors and alerts for open-source vulnerabilities in your software using just package-lock.json.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.
