Malicious Code Injection in muklis-45: A Threat to npm Ecosystem
Summary
MAL-2025-160830: Malicious code in muklis-45 (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
muklis-45 is an npm package that has been identified as part of a malicious campaign targeting the npm registry. This package is associated with the tea.xyz token reward initiative, which aims to inflate developer reputation scores through the automatic generation and publication of derivative packages. The malicious nature of muklis-45 lies in its ability to modify package metadata and continuously republish variants, thereby polluting the npm ecosystem.
Vulnerability Detail
The vulnerability in muklis-45 originates from its design to include autopublish scripts that alter the package.json file by removing private flags and changing version numbers. This allows the package to generate random names, often themed around Indonesian culture, and republish these variants to the npm registry. The ramifications of this vulnerability include the potential for developers to unknowingly install compromised packages, leading to further exploitation and degradation of the npm ecosystem.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall muklis-45If 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, you can avoid using the muklis-45 package and any other packages that may be associated with the tea.xyz campaign. Regularly audit your npm packages using tools like npm audit to identify and mitigate potential vulnerabilities.
Conclusion
The muklis-45 package poses a significant threat to the npm ecosystem due to its malicious code designed to manipulate package metadata and republish variants. It is essential for developers to remain vigilant, regularly audit their dependencies, and utilize tools like Vulert to monitor for vulnerabilities.
See every vulnerability recorded for muklis-45 →
FAQ
muklis-45 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 compromised packages, which may introduce malicious code into your project, potentially compromising security and functionality.
You can use Vulert, a tool that monitors and alerts for open-source vulnerabilities in real-time. By simply using your package-lock.json file, you can check if your application is affected by this vulnerability.
If you have installed muklis-45, you should immediately uninstall it using 'npm uninstall muklis-45' and review your other dependencies for potential vulnerabilities.
Yes, tools like npm audit and Vulert can help you identify and manage vulnerabilities in your npm packages effectively.
