Malicious Code Injection in muklis-54: npm Package Vulnerability
Summary
MAL-2025-160840: Malicious code in muklis-54 (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-54 package is part of a series of npm packages associated with the tea.xyz token reward campaign. These packages are designed to manipulate npm's ecosystem by generating and publishing derivative packages with randomized names. The primary function of muklis-54 is to inflate developer reputation scores for rewards, but it has been identified as containing malicious code that compromises the integrity of the npm registry.
Vulnerability Detail
The vulnerability in muklis-54 originates from its design to automatically modify package.json files, removing private flags and altering version numbers. This malicious payload generates random package names, primarily themed around Indonesian culture, and continuously republishes these variants to pollute the npm registry. The ramifications include potential security risks for developers who unknowingly use these packages, as well as damage to the overall trustworthiness of the npm ecosystem.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall muklis-54If 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-54 package and monitor your dependencies for any malicious activity. Consider using tools like Vulert to scan 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-54 package poses a significant risk due to its malicious code designed to manipulate the npm ecosystem. It is crucial for developers to remove this package and monitor their dependencies for vulnerabilities. Utilizing tools like Vulert can help maintain the security of your projects.
See every vulnerability recorded for muklis-54 →
FAQ
The muklis-54 package is an npm package involved in a token reward campaign that generates and publishes derivative packages to inflate developer reputation scores.
The vulnerability can compromise your project's integrity by introducing malicious code that modifies package files and floods the npm registry with unwanted packages.
You should remove the muklis-54 package from your project immediately and check for any other affected packages.
You can use tools like Vulert, which monitors your package-lock.json for open-source vulnerabilities in real-time.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by vulnerabilities without requiring any signup.
