Malicious Code Injection in aggressive_haddock_z3n Package
Summary
MAL-2025-99251: Malicious code in aggressive_haddock_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 aggressive_haddock_z3n package is part of the npm ecosystem, which is widely used for JavaScript package management. This package is associated with the tea.xyz token reward campaign, which has been known to flood the npm registry with malicious packages. These packages often contain scripts designed to manipulate package metadata and inflate developer reputation scores, making them a significant risk to developers and users alike.
Vulnerability Detail
The vulnerability in the aggressive_haddock_z3n package stems from its malicious payload that modifies the package.json file. It removes private flags, alters version numbers, and generates random package names, contributing to the pollution of the npm registry. This behavior not only compromises the integrity of the affected package but also poses a risk to users who may unknowingly install these malicious derivatives, leading to potential security breaches and loss of trust in the npm ecosystem.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall aggressive_haddock_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_haddock_z3n package and any packages that depend on it. Additionally, consider using npm audit to identify and address vulnerabilities in your project's dependencies.
Conclusion
The aggressive_haddock_z3n package poses a significant risk due to its malicious code designed to manipulate package metadata. It is essential for developers to be vigilant and remove any affected packages from their projects. Regularly updating dependencies and utilizing tools like Vulert can help maintain the security of your applications.
See every vulnerability recorded for aggressive_haddock_z3n →
FAQ
The aggressive_haddock_z3n package is an npm package that has been identified as malicious, associated with a campaign to inflate developer reputation scores through the publication of derivative packages.
This vulnerability can compromise the integrity of your project by introducing malicious code that modifies your package metadata and potentially leads to security breaches.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. By using the Vulert playground, you can check if your application is affected by this vulnerability without any signup.
If you have installed the aggressive_haddock_z3n package, it is crucial to remove it immediately and check for any other affected packages in your project.
Yes, tools like npm audit can help identify vulnerabilities in your project's dependencies, and services like Vulert provide real-time monitoring for open-source vulnerabilities.
