Malicious Code Injection in muklis-60 Package: npm Vulnerability Overview
Summary
MAL-2025-160847: Malicious code in muklis-60 (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-60 package is part of a series of packages that emerged during the tea.xyz token reward campaign, which aimed to inflate developer reputation scores on npm. These packages are designed to automate the generation and publication of derivative packages with randomized names, often compromising the integrity of the npm registry. The malicious behavior of muklis-60 includes modifying package.json files to remove private flags and changing version numbers, which can lead to significant security risks for developers using this package.
Vulnerability Detail
The vulnerability in the muklis-60 package originates from its design to automatically publish derivative packages with malicious intent. The payload modifies the package.json file to remove private flags, allowing unauthorized access and manipulation of the package. This can lead to the proliferation of malicious packages in the npm registry, potentially affecting other developers and users who may unknowingly install these compromised packages. The continuous republishing of variants further pollutes the npm ecosystem, making it difficult to track and manage legitimate packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall muklis-60If 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 the muklis-60 package and any other packages that are part of the tea.xyz token reward campaign. Additionally, consider using tools like Vulert to monitor your project 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-60 package poses a significant risk due to its malicious code that modifies package.json files and repopulates the npm registry with compromised packages. It is crucial for developers to remove this package and monitor their projects for vulnerabilities using tools like Vulert to ensure the integrity of their applications.
See every vulnerability recorded for muklis-60 →
FAQ
The muklis-60 package is part of a malicious campaign on npm that generates and publishes derivative packages to inflate developer reputation scores.
The vulnerability can lead to unauthorized access and manipulation of your project's dependencies, potentially introducing malicious code.
You should remove the muklis-60 package from your project immediately and check for any other affected packages.
You can use Vulert, which monitors your package-lock.json for open-source vulnerabilities in real-time. Visit https://vulert.com for more information.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by vulnerabilities without needing to sign up.
