Malicious Code Injection in emmahayes Package: A Threat to npm Ecosystem
Summary
MAL-2025-171158: Malicious code in emmahayes (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 emmahayes package is part of the npm ecosystem, which is widely used for JavaScript package management. It is designed to facilitate the development and sharing of JavaScript code. However, this package has been identified as part of a malicious campaign that aims to inflate developer reputation scores through the automatic generation and publication of derivative packages. This behavior poses a significant risk to developers and users relying on the integrity of npm packages.
Vulnerability Detail
The vulnerability in the emmahayes package originates from its association with the tea.xyz token reward campaign. The package contains malicious scripts that modify the package.json file by removing private flags, altering version numbers, and generating random package names. This leads to the continuous republishing of these variants, which pollutes the npm registry and compromises the security of the ecosystem. The ramifications include potential exposure to further malicious code and a degradation of trust in the npm registry.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall emmahayesIf 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 emmahayes package and look for alternative packages that provide similar functionality without the associated risks. Additionally, ensure that your package.json file is regularly audited for any unauthorized changes.
Conclusion
The emmahayes package poses a significant threat to the npm ecosystem due to its malicious code designed to manipulate package metadata and inflate developer reputation scores. Immediate action is required to remove this package and safeguard your projects from potential vulnerabilities. Utilizing tools like Vulert can help maintain the security of your software.
See every vulnerability recorded for emmahayes →
FAQ
The emmahayes package is an npm package used for JavaScript development, but it has been identified as malicious and part of a campaign to inflate developer reputation scores.
The malicious code modifies your package.json file and can lead to the publication of unauthorized packages, potentially compromising your project's security.
You should uninstall the emmahayes package immediately using the command npm uninstall emmahayes and check for any unauthorized changes in your project.
Yes, you can use Vulert, which monitors and alerts for open-source vulnerabilities in your software using just the package-lock.json file. You can check your application for vulnerabilities using the Vulert playground without any signup.
Regularly audit your dependencies, use tools like Vulert for monitoring, and stay updated on security advisories related to the packages you use.
