Malicious Code Injection in specified_haddock_z3n Package
Summary
MAL-2025-108994: Malicious code in specified_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 specified_haddock_z3n package is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to facilitate the automatic generation and publication of derivative packages, which can inflate developer reputation scores for token rewards. However, it has been identified as containing malicious code that compromises the integrity of the npm registry.
Vulnerability Detail
The vulnerability originates from the malicious code embedded within the specified_haddock_z3n package. This code modifies the package.json file to remove private flags, alters version numbers, and creates random package names, leading to the continuous republishing of these variants. The ramifications include pollution of the npm registry, potential security risks for developers using these packages, and a degradation 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 specified_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 remove the specified_haddock_z3n package from your project by executing: npm uninstall specified_haddock_z3n. This will prevent any malicious code from executing until a secure version is available.
Conclusion
The specified_haddock_z3n package has been identified as containing malicious code that poses a significant risk to developers and the npm ecosystem. It is crucial to take immediate action by updating or removing the package to safeguard your projects.
See every vulnerability recorded for specified_haddock_z3n →
FAQ
It is an npm package associated with the tea.xyz token reward campaign, designed to generate and publish derivative packages.
The malicious code modifies your package.json, removes private flags, and can lead to the pollution of the npm registry, affecting the integrity of your project.
You should uninstall the specified_haddock_z3n package immediately and check for any updates or patches.
Yes, you can use Vulert to monitor and alert in real-time for open-source vulnerabilities in your software. With Vulert, you can check if your application is affected by this vulnerability using the playground at Vulert Scanner.
Regularly update your packages, monitor for vulnerabilities using tools like Vulert, and review your package-lock.json file for any suspicious entries.
