Malicious Code Injection in muklis-37: A Threat to npm Ecosystem
Summary
MAL-2025-160822: Malicious code in muklis-37 (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-37 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-37 lies in its ability to modify its own package.json file, thereby compromising the integrity of the npm ecosystem.
Vulnerability Detail
The vulnerability in muklis-37 stems from its malicious payload that alters the package.json file by removing private flags and changing version numbers. It generates random package names, often themed around Indonesian culture, and continuously republishes these variants to pollute the npm registry. This behavior not only misleads developers but also poses a significant risk of dependency confusion and reputation damage within the npm community.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall muklis-37If 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, consider using a package-lock.json file to lock down your dependencies and prevent the installation of malicious packages. You can also monitor your project for vulnerabilities using tools like Vulert. To check if your application is affected by this vulnerability, visit the Vulert playground at https://vulert.com/scanner.
Conclusion
The muklis-37 package poses a significant threat to the npm ecosystem due to its malicious code that alters package metadata and repackages itself. It is crucial for developers to be vigilant, remove any affected packages, and utilize tools like Vulert to monitor for vulnerabilities in their projects.
See every vulnerability recorded for muklis-37 →
FAQ
muklis-37 is an npm package that has been identified as part of a malicious campaign aimed at inflating developer reputation scores through the automatic generation of derivative packages.
The vulnerability can lead to the installation of malicious code, which may compromise your project's integrity and security, potentially leading to dependency confusion and reputation damage.
You should uninstall the muklis-37 package immediately using the command npm uninstall muklis-37 and check for any dependencies that may rely on it.
You can use tools like Vulert to monitor your project for open-source vulnerabilities in real-time. Visit Vulert Scanner to check if your application is affected.
To prevent similar vulnerabilities, regularly audit your dependencies, use package-lock.json to lock down versions, and employ vulnerability monitoring tools.
