Malicious Code Injection in Emilydavies Package: npm Vulnerability Overview
Summary
MAL-2025-171147: Malicious code in emilydavies (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 'emilydavies' package is part of the npm ecosystem, which is widely used for JavaScript package management. This package has been identified as part of a malicious campaign that aims to exploit the npm registry by flooding it with derivative packages. These packages are designed to inflate developer reputation scores through automated publishing scripts, which can lead to significant issues within the ecosystem.
Vulnerability Detail
The vulnerability originates from a malicious payload embedded within the 'emilydavies' package. This payload modifies the package.json file to remove private flags, alters version numbers, and generates random package names, primarily themed around Indonesian culture. The scripts continuously republish these variants, polluting the npm registry and potentially compromising other packages and projects that depend on npm. The ramifications include loss of trust in the npm ecosystem, potential security risks for developers, and a cluttered registry that makes it difficult to find legitimate packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall emilydaviesIf 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 measure, you can avoid using the 'emilydavies' package and look for alternative packages that provide similar functionality without the associated risks. 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 'emilydavies' package poses a significant risk due to its malicious code designed to exploit the npm registry. It is crucial for developers to remove this package from their projects and monitor their dependencies for vulnerabilities. Utilizing tools like Vulert can help maintain the security of your applications.
See every vulnerability recorded for emilydavies →
FAQ
The 'emilydavies' package is an npm package that has been identified as part of a malicious campaign to exploit the npm registry.
The malicious code can modify your package.json file, remove private flags, and republish variants, leading to potential security risks and a polluted npm registry.
You should uninstall the 'emilydavies' package immediately using 'npm uninstall emilydavies' and check for any other affected packages.
Yes, you can use Vulert, which monitors and alerts for open-source vulnerabilities in your software using just package-lock.json.
You can use the Vulert playground at Vulert Scanner to check if your application is affected without needing to sign up.
