Malicious Code Injection in muklis-39: A Threat to npm Ecosystem
Summary
MAL-2025-160823: Malicious code in muklis-39 (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-39 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-39 lies in its ability to manipulate package metadata and proliferate harmful variants across the npm ecosystem.
Vulnerability Detail
The vulnerability in muklis-39 originates from its design to include autopublish scripts that modify the package.json file by removing private flags and altering version numbers. It generates random package names, often themed around Indonesian culture, and continuously republishes these variants to pollute the npm registry. This behavior can lead to a significant increase in malicious packages, potentially compromising the integrity of the npm ecosystem and affecting developers who unknowingly depend on these packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall muklis-39If 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 muklis-39 and any packages that depend on it. Additionally, consider using npm audit to identify and address vulnerabilities in your project's dependencies.
Conclusion
The discovery of malicious code in the muklis-39 package highlights the importance of vigilance in managing dependencies within the npm ecosystem. Developers should take proactive measures to remove affected packages and utilize tools like Vulert to monitor for vulnerabilities effectively.
See every vulnerability recorded for muklis-39 →
FAQ
muklis-39 is an npm package associated with a malicious campaign that aims to inflate developer reputation scores through the automatic generation of harmful packages.
Using muklis-39 can lead to the introduction of malicious code into your project, potentially compromising its security and integrity.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check your application without needing to sign up.
If you have installed muklis-39, you should remove it immediately and check for any other affected packages in your project.
Yes, tools like Vulert can help monitor your dependencies for vulnerabilities and provide alerts in real-time.
