Malicious Code Injection in Attractive Eagle Z3N Package
Summary
MAL-2025-93303: Malicious code in attractive_eagle_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 Attractive Eagle Z3N package is part of a series of npm packages that have been associated with the tea.xyz token reward campaign. These packages are designed to automate the generation and publication of derivative packages, often with randomized names, to inflate developer reputation scores for token rewards. This behavior raises concerns about the integrity of the npm registry and the potential for malicious exploitation.
Vulnerability Detail
The vulnerability stems from the presence of malicious code within the Attractive Eagle Z3N package. This code modifies the package.json file by removing private flags, altering version numbers, and generating random package names, which leads to the continuous republishing of variants. This not only pollutes the npm registry but also poses a risk of unintentional use of compromised packages by developers, potentially leading to further security issues.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall attractive_eagle_z3n
If 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 remove the Attractive Eagle Z3N package from your project by running: npm uninstall attractive_eagle_z3n. This will prevent any potential malicious code from executing until a secure version is available.
Conclusion
The Attractive Eagle Z3N package has been identified as containing malicious code that poses significant risks to developers and the integrity of the npm registry. It is crucial to take immediate action by updating or removing the package to mitigate these risks. Utilizing tools like Vulert can help monitor for such vulnerabilities in the future.
See every vulnerability recorded for attractive_eagle_z3n →
FAQ
The package contains malicious code that modifies package.json and floods the npm registry with derivative 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.
Using this package can lead to security vulnerabilities, including the risk of unintentional use of compromised packages and potential exposure of sensitive data.
Regularly audit your dependencies and use tools like Vulert to monitor for vulnerabilities in your open-source packages.
If an immediate update is not possible, consider removing the package from your project as a temporary measure until a secure version is available.