Malicious Code Injection in ethanmoore Package: npm Vulnerability Overview
Summary
MAL-2025-171178: Malicious code in ethanmoore (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 ethanmoore package is part of the npm ecosystem, which is widely used for JavaScript package management. This package, like many others, is intended to facilitate the development and distribution of JavaScript applications. However, it has been identified as part of a malicious campaign that aims to exploit npm's publishing capabilities, leading to potential security risks for developers and users alike.
Vulnerability Detail
The vulnerability in the ethanmoore package stems from its association with a malicious campaign that floods the npm registry with derivative packages. These packages contain scripts designed to automatically modify the package.json file, removing private flags and changing version numbers. This behavior can lead to the proliferation of malicious packages, which can compromise the integrity of applications relying on them. The origin of this vulnerability is linked to the tea.xyz token reward campaign, which incentivizes the creation of such malicious packages to inflate developer reputation scores.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall ethanmooreIf 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 ethanmoore package from your project by executing the following command: npm uninstall ethanmoore. This will prevent any malicious code from executing in your application until a safe version is released.
Conclusion
The ethanmoore package has been identified as a vector for malicious code injection, posing significant risks to developers and users. It is crucial to take immediate action by updating or removing the package to safeguard your applications. Utilizing tools like Vulert can further enhance your security posture by providing real-time vulnerability monitoring.
See every vulnerability recorded for ethanmoore →
FAQ
The ethanmoore package is a JavaScript package available on npm, primarily used for various development purposes. However, it has been linked to malicious activities.
The vulnerability can lead to the injection of malicious code into your application, potentially compromising its security and integrity.
Yes, you can use tools like Vulert, which monitors your package-lock.json file to alert you in real-time for open-source vulnerabilities.
If you cannot update the package, it is advisable to remove it from your project to avoid potential security risks.
You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without requiring any signup.
