Malicious Code Injection in muklis-58: A Threat to npm Ecosystem
Summary
MAL-2025-160844: Malicious code in muklis-58 (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-58' 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. This behavior aims to inflate developer reputation scores for token rewards, posing a significant risk to the integrity of the npm ecosystem.
Vulnerability Detail
The vulnerability in 'muklis-58' originates from its malicious payload, which modifies the package.json file to remove private flags, alters version numbers, and generates random Indonesian-themed package names. This results in the continuous republishing of variants, which pollutes the npm registry and can lead to compromised developer accounts and reputational damage.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall muklis-58If 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-58' package and any other packages associated with the tea.xyz campaign. Monitor your project for any unauthorized changes to the package.json file and revert them if necessary.
Conclusion
The 'muklis-58' package poses a significant threat to the npm ecosystem through its malicious behavior. It is crucial for developers to remain vigilant, regularly audit their dependencies, and utilize tools like Vulert to monitor for vulnerabilities. By taking proactive measures, developers can protect their projects from such threats.
See every vulnerability recorded for muklis-58 →
FAQ
The impact includes potential pollution of the npm registry, compromised developer accounts, and inflated reputation scores for malicious actors.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software. Check your application using the Vulert playground at Vulert Scanner.
There is no patch available for muklis-58 as it is a malicious package. The best course of action is to uninstall it.
You should immediately uninstall the package using 'npm uninstall muklis-58' and review your project for any unauthorized changes.
Regularly audit your dependencies, use tools like Vulert for real-time monitoring, and avoid installing unverified packages.
