Malicious Code Injection in muklis-57: A Threat to npm Packages
Summary
MAL-2025-160843: Malicious code in muklis-57 (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-57' is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to automate the generation and publication of derivative packages, which can inflate developer reputation scores for token rewards. However, it has been identified as containing malicious code that compromises the integrity of the npm registry.
Vulnerability Detail
The vulnerability in 'muklis-57' originates from its malicious payload, which modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior leads to the continuous republishing of variants, polluting the npm registry and potentially affecting other developers and users relying on the integrity of npm packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall muklis-57If 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 the 'muklis-57' package and monitor your dependencies for any similar malicious packages. Regularly audit your npm packages using 'npm audit' to identify and address vulnerabilities.
Conclusion
The 'muklis-57' package poses a significant threat due to its malicious code that alters package metadata and floods the npm registry with harmful variants. It is essential to remove this package and monitor your dependencies to maintain the security of your applications.
See every vulnerability recorded for muklis-57 →
FAQ
The impact includes potential pollution of the npm registry, which can lead to the proliferation of malicious packages and compromise the security of applications relying on npm.
You can use Vulert to monitor and alert for open-source vulnerabilities in your software. Visit the Vulert playground at Vulert Scanner to check your application without any signup.
If you have installed 'muklis-57', you should uninstall it immediately using 'npm uninstall muklis-57' and audit your other dependencies for vulnerabilities.
Vulert uses the package-lock.json file to monitor and alert in real-time for open-source vulnerabilities, providing an easy way to stay informed about potential threats.
There are no patches available for 'muklis-57' as it is a malicious package. The best course of action is to remove it from your project.
