Malicious Code Injection in muklis-14: A Threat to npm Ecosystem
Summary
MAL-2025-160797: Malicious code in muklis-14 (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-14 is part of the npm ecosystem, which is widely used for JavaScript package management. It is designed to facilitate the development and sharing of code. However, this package has been identified as part of a malicious campaign that aims to exploit the npm registry by flooding it with derivative packages. This behavior not only affects the integrity of the npm ecosystem but also poses risks to developers and users relying on these packages.
Vulnerability Detail
The vulnerability in muklis-14 originates from its association with a token reward campaign that has been observed to flood the npm registry. The malicious code embedded in this package modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This leads to the continuous republishing of variants, which pollutes the npm registry and can inflate developer reputation scores fraudulently. The ramifications include potential security risks for users who unknowingly install these malicious packages, as well as a degradation of trust in the npm ecosystem.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall muklis-14If 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-14 package and instead look for alternative packages that provide similar functionality without the associated risks. Always verify the integrity and reputation of packages before installation.
Conclusion
The muklis-14 package poses a significant threat to the npm ecosystem due to its malicious code that modifies package metadata and floods the registry. It is crucial for developers to be vigilant, remove affected packages, and utilize monitoring tools like Vulert to safeguard their applications.
See every vulnerability recorded for muklis-14 →
FAQ
Muklis-14 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 lead to the installation of malicious code, which may compromise the security and integrity of your application.
You should uninstall muklis-14 immediately using 'npm uninstall muklis-14' and check your application for any other affected packages.
You can use tools like Vulert, which monitors your package-lock.json file to alert you in real-time for open-source vulnerabilities.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.
