Malicious Code Exploit in empty_mule_dumbs Package: npm Vulnerability Overview
Summary
MAL-2025-102075: Malicious code in empty_mule_dumbs (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 empty_mule_dumbs package is part of a series of npm packages that emerged during the tea.xyz token reward campaign. These packages are designed to manipulate the npm registry by generating and publishing numerous derivative packages with randomized names. This behavior is intended to inflate developer reputation scores for token rewards, making the package a potential vector for malicious activities.
Vulnerability Detail
The vulnerability in the empty_mule_dumbs package originates from its malicious code, which modifies the package.json file to remove private flags and alters version numbers. It generates random package names, often themed around Indonesian culture, and continuously republishes these variants to pollute the npm registry. This can lead to a compromised development environment, where developers may unknowingly install malicious packages, risking their applications and data.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall empty_mule_dumbsIf 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 remove the empty_mule_dumbs package from your project by executing: npm uninstall empty_mule_dumbs. This will prevent any malicious code from executing until a secure version is available.
Conclusion
The empty_mule_dumbs package poses a significant risk due to its malicious code designed to manipulate the npm registry. Developers should take immediate action to remove the package and monitor their projects for any vulnerabilities. Utilizing tools like Vulert can help maintain the security of your open-source dependencies.
See every vulnerability recorded for empty_mule_dumbs →
FAQ
The empty_mule_dumbs package is an npm package that is part of a malicious campaign to inflate developer reputation scores by flooding the npm registry with derivative packages.
The vulnerability can lead to the installation of malicious code that modifies your package.json file, potentially compromising your application and its dependencies.
If you have installed the empty_mule_dumbs package, it is crucial to uninstall it immediately and check for any other affected packages in your project.
You can use tools like Vulert, which monitors your package-lock.json file to alert you in real-time for open-source vulnerabilities. You can also check your application against known vulnerabilities using the Vulert playground.
To prevent similar vulnerabilities, regularly audit your dependencies, use tools like Vulert for monitoring, and stay updated with security advisories from the npm registry.
