Malicious Code Injection in muklis-32: A Threat to npm Packages
Summary
MAL-2025-160817: Malicious code in muklis-32 (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-32 package is part of a broader ecosystem within npm, primarily associated with the tea.xyz token reward campaign. This package, like others in its category, is designed to automate the generation and publication of derivative packages. Its functionality is compromised by malicious scripts that aim to inflate developer reputation scores through deceptive practices.
Vulnerability Detail
The vulnerability in muklis-32 stems from the presence of malicious code that modifies the package.json file. This code removes private flags, alters version numbers, and generates random package names, leading to the continuous republishing of these variants. The origin of this issue is linked to the tea.xyz token reward campaign, which has been known to flood the npm registry with such packages. The ramifications include potential pollution of the npm registry, loss of developer reputation, and exposure to further malicious activities.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall muklis-32If 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 prevent the installation of muklis-32 by using npm's package-lock.json file to monitor dependencies. You can also use the following command to uninstall the package: npm uninstall muklis-32.
Conclusion
The muklis-32 package poses a significant threat due to its malicious code that alters package metadata and floods the npm registry. It is crucial to remove this package from your projects and stay vigilant for any updates or patches. Utilizing tools like Vulert can help in monitoring your dependencies for vulnerabilities.
See every vulnerability recorded for muklis-32 →
FAQ
Muklis-32 is an npm package associated with the tea.xyz token reward campaign, designed to automate the generation of derivative packages.
The vulnerability can lead to the pollution of the npm registry and may expose your project to further malicious activities.
You should uninstall muklis-32 immediately and monitor your project for any unusual activity.
Yes, you can use tools like Vulert, which monitors and alerts for open-source vulnerabilities in real-time using your package-lock.json.
You can use the Vulert playground at Vulert Scanner to check if your application is affected without requiring any signup.
