Malicious Code Injection in muklis-23 Package: A Threat to npm Users
Summary
MAL-2025-160807: Malicious code in muklis-23 (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-23 package is part of the npm ecosystem, typically used for various JavaScript applications. However, it has been identified as part of a malicious campaign that aims to exploit the npm registry by flooding it with derivative packages. This package is associated with the tea.xyz token reward initiative, which incentivizes developers to inflate their reputation scores through automated publishing scripts.
Vulnerability Detail
The vulnerability in the muklis-23 package stems from its malicious code that modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior is designed to create and republish numerous variants of the package, ultimately polluting the npm registry and potentially compromising the integrity of other packages. The malicious payload can lead to significant security risks for developers and users relying on npm packages, as it undermines the trustworthiness of the ecosystem.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall muklis-23If 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-23 package and monitor your project for any dependencies that may have been affected by this malicious package. Regularly audit your package-lock.json file to identify and remove any suspicious packages.
Conclusion
The muklis-23 package poses a significant threat to the npm ecosystem due to its malicious code designed to manipulate package configurations and flood the registry. It is essential for developers to remove this package from their projects and monitor for any potential impacts on their applications. Utilizing tools like Vulert can help maintain the security of your open-source dependencies.
See every vulnerability recorded for muklis-23 →
FAQ
The muklis-23 package is an npm package that has been identified as part of a malicious campaign to flood the npm registry with derivative packages.
The vulnerability can compromise the integrity of your project by introducing malicious code that alters package configurations and floods the npm registry.
You should uninstall the muklis-23 package immediately using the command npm uninstall muklis-23 and check for any other affected dependencies.
Yes, you can use Vulert to monitor your project for open-source vulnerabilities in real-time by analyzing your package-lock.json file.
You can use the Vulert playground at Vulert Scanner to check if your application is affected by the muklis-23 vulnerability without needing to sign up.
