Malicious Code Injection in extra_emu_z3n: A Threat to npm Packages
Summary
MAL-2025-102427: Malicious code in extra_emu_z3n (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 package 'extra_emu_z3n' is part of the npm ecosystem, which is widely used for JavaScript package management. It is often utilized in various applications to enhance functionality and streamline development processes. However, this package has been identified as part of a malicious campaign that aims to exploit the npm registry by flooding it with derivative packages that can harm developers and users alike.
Vulnerability Detail
The vulnerability in 'extra_emu_z3n' originates from its association with the tea.xyz token reward campaign, which has been linked to the distribution of malicious packages on npm. These packages contain scripts designed to automatically generate and publish numerous derivative packages with altered names and metadata. The malicious payload modifies the package.json file to remove private flags, changes version numbers, and continuously republishes variants, leading to pollution of the npm registry and potential security risks for users who inadvertently install these packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall extra_emu_z3nIf 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 'extra_emu_z3n' package and look for alternative packages that provide similar functionality without the associated risks. Additionally, consider using tools like Vulert to monitor your package-lock.json for vulnerabilities.
Conclusion
The 'extra_emu_z3n' package poses a significant risk due to its malicious code that alters package metadata and floods the npm registry. It is essential to remove this package and monitor your dependencies to ensure the security of your applications. Utilizing tools like Vulert can help in identifying and mitigating such vulnerabilities effectively.
See every vulnerability recorded for extra_emu_z3n →
FAQ
The main issue is that it contains malicious code that modifies package metadata and floods the npm registry with derivative packages.
You can use Vulert's playground at Vulert Scanner to check if your application is affected without needing to sign up.
You should remove the package immediately and monitor your project for any unusual behavior.
Yes, consider researching and using other npm packages that provide similar functionality without the associated risks.
Regularly audit your dependencies, use tools like Vulert for real-time monitoring, and stay informed about security advisories.
