Malicious Code Injection in angry_aardvark_z3n: A Threat to npm Packages
Summary
MAL-2025-99468: Malicious code in angry_aardvark_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 'angry_aardvark_z3n' is part of the npm ecosystem, which is widely used for JavaScript package management. This package has been identified as part of a malicious campaign aimed at exploiting npm's publishing capabilities. It is designed to automatically generate and publish derivative packages with randomized names, which can lead to reputation inflation for developers involved in the tea.xyz token reward campaign.
Vulnerability Detail
The vulnerability in 'angry_aardvark_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, altering version numbers, and generating random package names. This not only pollutes the npm registry but also poses a risk of unintentional dependency on malicious packages by developers who may unknowingly install these variants.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall angry_aardvark_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 'angry_aardvark_z3n' package altogether. If it is already included in your project, consider removing it from your dependencies by executing: 'npm uninstall angry_aardvark_z3n'. Additionally, monitor your package-lock.json file for any unintended dependencies that may have been introduced.
Conclusion
The 'angry_aardvark_z3n' package poses a significant risk due to its malicious code designed to exploit npm's publishing system. It is crucial for developers to stay vigilant, update their dependencies, and utilize tools like Vulert to monitor for vulnerabilities in their projects.
See every vulnerability recorded for angry_aardvark_z3n →
FAQ
The vulnerability involves malicious code that modifies package.json files 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 any signup.
Using this package can lead to unintentional installation of malicious variants, compromising your application's integrity and security.
Regularly audit your dependencies and use tools like Vulert to monitor for vulnerabilities in your open-source packages.
Uninstall the package immediately using 'npm uninstall angry_aardvark_z3n' and check your project for any affected dependencies.
