Malicious Code Injection in muklis-31: A Threat to npm Ecosystem
Summary
MAL-2025-160816: Malicious code in muklis-31 (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-31' is part of a series of malicious npm packages associated with the tea.xyz token reward campaign. These packages are designed to manipulate the npm registry by creating and publishing numerous derivative packages with randomized names. The primary functionality of these packages is to inflate developer reputation scores for token rewards, which poses a significant risk to the integrity of the npm ecosystem.
Vulnerability Detail
The vulnerability in 'muklis-31' stems from its malicious code that modifies the package.json file by removing private flags and altering version numbers. It generates random package names, primarily themed around Indonesian culture, and continuously republishes these variants to pollute the npm registry. This behavior can lead to a compromised development environment, where developers may unknowingly use these malicious packages, potentially exposing their applications to further vulnerabilities.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall muklis-31If 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-31' package and any other packages that are part of the tea.xyz token reward campaign. Monitor your project for any dependencies that may have been inadvertently included and remove them promptly.
Conclusion
The 'muklis-31' package poses a significant threat to the npm ecosystem due to its malicious behavior aimed at inflating developer reputation scores. It is essential for developers to be vigilant, regularly monitor their dependencies, and take immediate action to remove any affected packages to safeguard their applications.
See every vulnerability recorded for muklis-31 →
FAQ
Using the muklis-31 package can lead to the exposure of your application to malicious code, which may compromise its security and integrity.
You can use tools like Vulert, which monitors your package-lock.json for vulnerabilities in real-time. You can also check your application using the Vulert playground without any signup.
If you have used muklis-31, it is crucial to uninstall it immediately and review your project for any other potentially malicious dependencies.
Yes, tools like Vulert can help monitor and alert you to open-source vulnerabilities in your software without requiring access to your code.
It is advisable to regularly check for vulnerabilities, especially after adding new packages or updating existing ones, to ensure the security of your application.
