Malicious Code Injection in muklis-33: A Threat to npm Ecosystem
Summary
MAL-2025-160818: Malicious code in muklis-33 (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-33' is part of a broader campaign associated with the tea.xyz token reward initiative, which has been known to flood the npm registry with malicious packages. These packages are designed to manipulate developer reputation scores by automatically generating and publishing derivative packages with randomized names. The presence of such malicious code poses a significant risk to developers and the integrity of the npm ecosystem.
Vulnerability Detail
The vulnerability in 'muklis-33' stems from its malicious payload that modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior not only compromises the security of the affected applications but also contributes to the pollution of the npm registry, making it difficult for developers to trust the packages they use. The origin of this vulnerability is linked to the tea.xyz token reward campaign, which incentivizes the creation of such malicious packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall muklis-33If 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 'muklis-33' and look for alternative packages that provide similar functionality without the associated risks. Regularly audit your package dependencies to ensure they are secure.
Conclusion
The 'muklis-33' package poses a significant threat to the npm ecosystem due to its malicious behavior. It is crucial for developers to remain vigilant, regularly audit their dependencies, and utilize tools like Vulert to monitor for vulnerabilities. Removing such packages promptly can help maintain the integrity and security of your applications.
See every vulnerability recorded for muklis-33 →
FAQ
'muklis-33' is a malicious npm package that is part of a campaign to inflate developer reputation scores through the automatic generation and publication of derivative packages.
The package modifies your package.json file, removes private flags, and can lead to the pollution of the npm registry, compromising the security of your application.
You should uninstall 'muklis-33' immediately using the command 'npm uninstall muklis-33' and check for any alternative packages.
You can use Vulert, which monitors and alerts in real-time for open-source vulnerabilities using just your package-lock.json. You can check your application for vulnerabilities without any signup at the Vulert playground.
No, there are no patches available for 'muklis-33' as it is a malicious package. The best course of action is to remove it from your project.
