Malicious Code Injection in muklis-36 Package: A Threat to npm Users
Summary
MAL-2025-160821: Malicious code in muklis-36 (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-36 package is part of a broader campaign that exploits the npm ecosystem by flooding it with malicious packages. These packages are designed to manipulate developer reputation scores through automated publishing scripts. The primary functionality of muklis-36 is to generate and publish derivative packages with randomized names, which can lead to significant pollution of the npm registry and compromise the integrity of the ecosystem.
Vulnerability Detail
The vulnerability in the muklis-36 package originates from its association with the tea.xyz token reward campaign. It contains malicious scripts that modify the package.json file by removing private flags and altering version numbers. Additionally, it generates random package names, often themed around Indonesian culture, and continuously republishes these variants. This behavior not only inflates developer reputation scores but also poses a risk of introducing untrusted code into applications that depend on these packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall muklis-36If 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, avoid using the muklis-36 package and any other packages that are part of the tea.xyz campaign. Regularly audit your dependencies using tools like npm audit to identify and mitigate risks associated with malicious packages.
Conclusion
The muklis-36 package poses a significant threat to the npm ecosystem due to its malicious behavior aimed at inflating developer reputation scores. It is crucial for developers to remain vigilant, regularly audit their dependencies, and utilize tools like Vulert to ensure their applications are secure from such vulnerabilities.
See every vulnerability recorded for muklis-36 →
FAQ
The muklis-36 package is a malicious npm package designed to manipulate developer reputation scores by flooding the npm registry with derivative packages.
The vulnerability can introduce untrusted code into your application, potentially leading to security breaches and instability.
You can use tools like Vulert to monitor your package-lock.json file for vulnerabilities. Visit Vulert Scanner to check your application without any signup.
Immediately uninstall the muklis-36 package using npm uninstall muklis-36 and review your dependencies for any other malicious packages.
Yes, tools like Vulert can help monitor and alert you in real-time for open-source vulnerabilities in your software.
