Malicious Code Injection in potential_haddock_z3n Package - npm Vulnerability Overview
Summary
MAL-2025-89484: Malicious code in potential_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 potential_haddock_z3n package is part of the npm ecosystem, primarily utilized for JavaScript development. It is associated with the tea.xyz token reward campaign, which has been linked to a series of malicious packages flooding the npm registry. These packages are designed to manipulate developer reputation scores by automatically generating and publishing derivative packages with randomized names.
Vulnerability Detail
This vulnerability originates from the malicious intent behind the potential_haddock_z3n package, which contains scripts that modify the package.json file to remove private flags, alter version numbers, and generate random package names. The continuous republishing of these variants leads to pollution of the npm registry, potentially compromising the integrity of the ecosystem and affecting developers relying on legitimate packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall potential_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 potential_haddock_z3n package and instead look for alternative packages that provide similar functionality without the associated risks. Additionally, you can monitor your project's dependencies using tools like Vulert, which can alert you to vulnerabilities in real-time.
Conclusion
The potential_haddock_z3n package poses a significant risk due to its malicious code designed to manipulate the npm registry. It is crucial for developers to remove this package and monitor their dependencies for vulnerabilities. Utilizing tools like Vulert can enhance your project's security posture.
See every vulnerability recorded for potential_haddock_z3n →
FAQ
The potential_haddock_z3n package is an npm package associated with the tea.xyz token reward campaign, known for its malicious behavior.
This vulnerability can lead to the pollution of the npm registry, potentially compromising the integrity of your project's dependencies and affecting your development environment.
You should remove the potential_haddock_z3n package from your project and monitor for any updates or patches that may be released.
Yes, Vulert allows you to monitor and alert for open-source vulnerabilities in your software using just the package-lock.json file. You can check your application for vulnerabilities without any signup at the Vulert playground.
Regularly audit your project's dependencies, use tools like Vulert for real-time monitoring, and stay informed about security advisories related to the packages you use.
