Malicious Code Injection in muklis-34: A Threat to npm Packages
Summary
MAL-2025-160819: Malicious code in muklis-34 (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-34 is part of the npm ecosystem, which is widely used for JavaScript package management. It is associated with the tea.xyz token reward campaign, which has been known to flood the npm registry with malicious packages. These packages often contain scripts designed to manipulate package metadata and inflate developer reputation scores for token rewards.
Vulnerability Detail
The vulnerability in muklis-34 originates from its association with a malicious campaign that employs autopublish scripts to modify package.json files. This includes removing private flags, altering version numbers, and generating random package names. The continuous republishing of these variants pollutes the npm registry, potentially leading to security risks for developers who unknowingly use these packages. The malicious payload can compromise the integrity of projects relying on this package, making it essential for developers to be vigilant.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall muklis-34If 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, avoid using the muklis-34 package and consider using alternative packages that provide similar functionality without the associated risks. Additionally, regularly audit your dependencies using tools like npm audit to identify and address vulnerabilities.
Conclusion
The muklis-34 package poses a significant risk due to its malicious code designed to manipulate npm package metadata. It is essential for developers to remove this package from their projects and stay vigilant by monitoring their dependencies for vulnerabilities. Utilizing tools like Vulert can aid in maintaining the security of your applications.
See every vulnerability recorded for muklis-34 →
FAQ
Muklis-34 is an npm package that has been identified as part of a malicious campaign to manipulate the npm registry and inflate developer reputation scores.
The vulnerability can compromise the integrity of your project by introducing malicious code that alters package metadata and republishing variants that may conflict with your dependencies.
You should uninstall the muklis-34 package immediately using the command npm uninstall muklis-34 and check your project for any other affected packages.
You can use tools like npm audit to scan your project for vulnerabilities. Additionally, Vulert offers real-time monitoring for open-source vulnerabilities using your package-lock.json file.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without requiring any signup.
