Malicious Code Injection in muklis-3 Package: A Threat to npm Users
Summary
MAL-2025-160814: Malicious code in muklis-3 (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-3 package is part of the npm ecosystem, often used in JavaScript projects for various functionalities. However, it has been identified as part of a malicious campaign that aims to inflate developer reputation scores through the automatic generation and publication of derivative packages. This behavior not only clutters the npm registry but also poses security risks to users who may unknowingly install these compromised packages.
Vulnerability Detail
The vulnerability in the muklis-3 package stems from its association with a malicious campaign that modifies the package.json file to remove private flags and change version numbers. It generates random package names, often themed around Indonesian culture, and continuously republishes these variants, polluting the npm registry. This can lead to developers inadvertently installing malicious code, which may compromise their applications and data.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall muklis-3If 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-3 package and replace it with an alternative package that provides similar functionality without the associated risks. Additionally, regularly audit your package dependencies using tools like npm audit to identify and mitigate vulnerabilities.
Conclusion
The muklis-3 package poses a significant security risk due to its malicious code injection practices. It is crucial for developers to remove this package and monitor their dependencies for vulnerabilities. Utilizing tools like Vulert can help maintain the security of your applications by providing real-time alerts on open-source vulnerabilities.
See every vulnerability recorded for muklis-3 →
FAQ
The muklis-3 package is an npm package that has been identified as part of a malicious campaign to inflate developer reputation scores through the automatic generation of derivative packages.
The vulnerability can lead to the installation of malicious code, potentially compromising your application's security and integrity.
You should remove the muklis-3 package from your project and check for any other affected packages. Use npm uninstall muklis-3 to remove it.
You can use tools like npm audit to scan your project for vulnerabilities. Additionally, Vulert can monitor your package-lock.json for real-time alerts on open-source vulnerabilities.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without requiring any signup.
