Malicious Code Injection in muklis-40: A Threat to npm Packages
Summary
MAL-2025-160825: Malicious code in muklis-40 (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-40' is part of a series of npm packages associated with the tea.xyz token reward campaign. These packages are designed to manipulate the npm registry by automatically generating and publishing derivative packages with randomized names. This behavior is intended to inflate developer reputation scores for rewards in the tea protocol, making it a significant concern for developers relying on npm for package management.
Vulnerability Detail
The vulnerability in 'muklis-40' originates from its malicious design, which includes scripts that modify the package.json file to remove private flags, alter version numbers, and generate random package names. This leads to the continuous republishing of variants that pollute the npm registry, potentially compromising the integrity of other packages and affecting developers' workflows. The malicious payload can also lead to unauthorized access to sensitive information if private flags are removed.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall muklis-40If 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 measure, you can avoid using 'muklis-40' and any other packages associated with the tea.xyz token reward campaign. Monitor your package-lock.json file for any unauthorized changes and consider using tools like Vulert to track vulnerabilities in your dependencies.
Conclusion
The 'muklis-40' package poses a significant threat due to its malicious code designed to manipulate the npm registry. It is essential for developers to be vigilant, remove any affected packages, and utilize tools like Vulert to monitor for vulnerabilities in their projects. Regular updates and careful management of dependencies can help mitigate these risks.
See every vulnerability recorded for muklis-40 →
FAQ
'muklis-40' is an npm package involved in a malicious campaign that aims to manipulate the npm registry by publishing derivative packages.
The vulnerability can lead to the pollution of the npm registry, unauthorized access to sensitive information, and potential disruptions in your development workflow.
You should uninstall 'muklis-40' immediately using the command 'npm uninstall muklis-40' and check your project for any other affected packages.
You can use tools like Vulert, which monitors your package-lock.json file for vulnerabilities in real-time without requiring code access or installation.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.
