Malicious Code Injection in muklis-42 Package: npm Vulnerability Overview
Summary
MAL-2025-160827: Malicious code in muklis-42 (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-42 package is part of a series of npm packages associated with the tea.xyz token reward campaign. These packages are designed to automate the generation and publication of derivative packages, often with randomized names, to inflate developer reputation scores for token rewards. The functionality of muklis-42 is compromised due to its malicious payload, which modifies package.json files and republishes variants to pollute the npm registry.
Vulnerability Detail
The vulnerability in the muklis-42 package originates from its association with a malicious campaign that floods the npm registry with derivative packages. The malicious code alters the package.json file by removing private flags, changing version numbers, and generating random package names. This can lead to significant ramifications, including the pollution of the npm registry and potential security risks for developers who unknowingly use these compromised packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall muklis-42If 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-42 package and any other packages associated with the tea.xyz token reward campaign. Regularly audit your dependencies to ensure that no malicious packages are included.
Conclusion
The muklis-42 package poses a significant threat due to its malicious code that alters package.json files and floods the npm registry with compromised packages. It is crucial to remove this package from your project and regularly audit your dependencies to maintain security.
See every vulnerability recorded for muklis-42 →
FAQ
The muklis-42 package is an npm package that is part of a malicious campaign aimed at inflating developer reputation scores through automated package publishing.
The vulnerability can lead to the pollution of the npm registry and may introduce security risks if your project unknowingly depends on compromised packages.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software. Visit Vulert Scanner to check if your application is affected without needing to sign up.
You should uninstall the muklis-42 package immediately using the command 'npm uninstall muklis-42' and audit your dependencies for any other malicious packages.
Yes, tools like Vulert can help monitor your project for vulnerabilities in real-time using just the package-lock.json file.
