Malicious Code Injection in emilyturner Package: A Threat to npm Users
Summary
MAL-2025-171153: Malicious code in emilyturner (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 emilyturner 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 manipulate the npm registry by creating and publishing numerous derivative packages with deceptive names. This behavior not only affects the integrity of the npm ecosystem but also poses a significant risk to developers who may unknowingly use these compromised packages.
Vulnerability Detail
The vulnerability in the emilyturner package stems from its association with a malicious campaign that modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This allows the package to continuously republish variants, thereby polluting the npm registry and inflating developer reputation scores for token rewards. The malicious code can lead to the unintentional use of compromised packages, which may contain further vulnerabilities or harmful code.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall emilyturnerIf 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 emilyturner package and any other packages that may have been published as part of the same malicious campaign. Regularly audit your package dependencies to identify and remove any suspicious packages.
Conclusion
The emilyturner package poses a significant threat to npm users due to its malicious behavior aimed at manipulating the npm registry. It is crucial for developers to remain vigilant, regularly audit their dependencies, and utilize tools like Vulert to monitor for vulnerabilities. By taking proactive measures, developers can safeguard their projects from potential threats.
See every vulnerability recorded for emilyturner →
FAQ
The emilyturner package is an npm package that has been identified as part of a malicious campaign aimed at manipulating the npm registry.
The malicious code can lead to the unintentional use of compromised packages, which may introduce vulnerabilities or harmful behavior into your project.
You can use Vulert, a tool that monitors and alerts for open-source vulnerabilities in your software. By analyzing your package-lock.json file, Vulert can help you identify affected packages without requiring code access.
You should uninstall the emilyturner package immediately and audit your project for any other potentially compromised packages.
No, there is no patch available for the emilyturner package as it is part of a malicious campaign. The best course of action is to remove it from your project.
