Malicious Code Injection in aggressive_emu_z3n: A Threat to npm Packages
Summary
MAL-2025-99250: Malicious code in aggressive_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
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
Background
The package 'aggressive_emu_z3n' is part of a series of npm packages that have been linked to the tea.xyz token reward campaign. These packages are designed to manipulate the npm registry by generating and publishing derivative packages with randomized names. This behavior is intended to inflate developer reputation scores for rewards associated with the tea protocol. The package's functionality is compromised due to the presence of malicious scripts that alter its metadata and behavior.
Vulnerability Detail
The vulnerability in 'aggressive_emu_z3n' originates from its association with a malicious campaign that floods the npm registry with derivative packages. The malicious payload modifies the package.json file by removing private flags, changing version numbers, and generating random package names. This not only pollutes the npm registry but also poses a risk to developers who may unknowingly install these compromised packages, leading to potential security breaches and loss of integrity in their applications.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall aggressive_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 'aggressive_emu_z3n' package until a secure version is released. Additionally, consider using alternative packages that provide similar functionality without the associated risks.
Conclusion
The 'aggressive_emu_z3n' package poses a significant security risk due to its malicious code that alters package metadata and floods the npm registry. Developers should take immediate action to update or remove this package and utilize tools like Vulert to monitor their applications for vulnerabilities.
See every vulnerability recorded for aggressive_emu_z3n →
FAQ
The vulnerability involves malicious code that alters the package's metadata and floods the npm registry with compromised packages.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check your application without needing to sign up.
If you have installed this package, it is recommended to remove it and update your dependencies to ensure your application is secure.
While specific exploits have not been detailed, the manipulation of package metadata can lead to broader security issues, including unauthorized access and data breaches.
Vulert uses your package-lock.json file to monitor for vulnerabilities in your open-source dependencies and provides real-time alerts.
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
