Malicious Code Injection in muklis-11: A Threat to npm Ecosystem
Summary
MAL-2025-160794: Malicious code in muklis-11 (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-11' is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. It is designed to facilitate the automatic generation and publication of derivative packages, which can inflate developer reputation scores. This package, like others in the campaign, is known for its malicious behavior, including modifying package metadata and republishing variants to pollute the npm registry.
Vulnerability Detail
The vulnerability in 'muklis-11' originates from its malicious code, which modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior is intended to create a flood of derivative packages in the npm registry, potentially harming the integrity of the ecosystem and misleading developers regarding package reliability. The malicious payload can lead to unauthorized access and manipulation of project dependencies, posing significant risks to applications relying on affected packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall muklis-11If 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-11' and any packages that depend on it. Additionally, consider using a tool like Vulert to monitor your package-lock.json for vulnerabilities. You can check if your application is affected by this vulnerability using the Vulert playground at https://vulert.com/scanner without any signup.
Conclusion
The 'muklis-11' package poses a significant threat to the npm ecosystem due to its malicious code that alters package metadata and floods the registry with derivative packages. It is crucial for developers to remove this package and monitor their dependencies to maintain application security.
See every vulnerability recorded for muklis-11 →
FAQ
'muklis-11' is an npm package involved in a token reward campaign that automates the creation and publication of derivative packages.
The vulnerability can lead to unauthorized modifications of your package dependencies, potentially compromising your application's security and reliability.
You can use the Vulert playground at Vulert Scanner to check your application for vulnerabilities without needing to sign up.
Uninstall 'muklis-11' and any related packages, and ensure your package-lock.json file is clean of references to this package. Regularly monitor your dependencies for vulnerabilities.
There is no patch for 'muklis-11' as it is a malicious package. The best course of action is to remove it from your project.
