Malicious Code Injection in Emilyjackson Package: A Threat to npm Users
Summary
MAL-2025-171149: Malicious code in emilyjackson (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 'emilyjackson' 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 process by providing reusable code. However, it has been identified as part of a malicious campaign that exploits npm's publishing capabilities, leading to significant security concerns for developers and users alike.
Vulnerability Detail
The vulnerability in the 'emilyjackson' package originates from its association with the tea.xyz token reward campaign. This package contains malicious scripts that modify the package.json file to remove private flags, alter version numbers, and generate random package names. The scripts are designed to automatically republish these variants, thereby polluting the npm registry and potentially compromising the integrity of other packages. The ramifications include the risk of developers unknowingly using compromised packages, leading to security breaches in their applications.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall emilyjacksonIf 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 'emilyjackson' package altogether and look for alternative packages that provide similar functionality without the associated risks. Always verify the integrity and reputation of packages before including them in your project.
Conclusion
The 'emilyjackson' package poses a significant security risk due to its malicious code designed to manipulate npm package configurations. It is essential for developers to remove this package from their projects and to regularly monitor their dependencies for vulnerabilities. Utilizing tools like Vulert can help maintain the security of your applications.
See every vulnerability recorded for emilyjackson →
FAQ
The 'emilyjackson' package is an npm package that has been identified as part of a malicious campaign aimed at exploiting the npm registry.
If your application uses the 'emilyjackson' package, it may be at risk of security breaches due to the malicious code that alters package configurations and republish variants.
You should uninstall the 'emilyjackson' package immediately using 'npm uninstall emilyjackson' and check your project for any other compromised packages.
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 vulnerabilities using the Vulert playground without any signup.
Yes, you should look for alternative packages that provide similar functionality but have a good reputation and are actively maintained.
