Malicious Code Injection in breakable_haddock_z3n: A Threat to npm Packages
Summary
MAL-2025-93425: Malicious code in breakable_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 package 'breakable_haddock_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 that aims to exploit npm's publishing capabilities. It is designed to generate and publish derivative packages with randomized names, thereby inflating developer reputation scores for token rewards in the tea.xyz protocol. The malicious nature of this package poses a significant risk to the integrity of the npm registry and the security of applications relying on it.
Vulnerability Detail
The vulnerability in 'breakable_haddock_z3n' originates from its association with the tea.xyz token reward campaign. The package contains scripts that automatically modify the package.json file by removing private flags, changing version numbers, and generating random package names. This behavior leads to the continuous republishing of variants, which pollutes the npm registry and can potentially introduce malicious code into dependent applications. The ramifications include compromised application security, loss of developer reputation, and a cluttered npm ecosystem.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall breakable_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 'breakable_haddock_z3n' package and look for alternative packages that provide similar functionality without the associated risks. Additionally, you can monitor your project for any unintended changes in the package.json file and revert them if necessary.
Conclusion
The 'breakable_haddock_z3n' package poses a significant risk due to its malicious code designed to manipulate npm's publishing system. It is crucial for developers to be aware of this vulnerability, take immediate action to remove the package, and utilize tools like Vulert to monitor their applications for potential threats. Staying informed and proactive is essential in maintaining the security of your software.
See every vulnerability recorded for breakable_haddock_z3n →
FAQ
It is an npm package that has been identified as part of a malicious campaign to inflate developer reputation scores through automated publishing of derivative packages.
The vulnerability can lead to the introduction of malicious code into your application, compromising its security and integrity.
You should uninstall the 'breakable_haddock_z3n' package immediately and monitor your project for any changes made to the package.json file.
Yes, you can use Vulert, which monitors and alerts in real-time for open-source vulnerabilities in your software using just package-lock.json. You can check if your application is affected by this vulnerability using the Vulert playground.
You can use the Vulert playground at Vulert Scanner to check if your application is affected by the 'breakable_haddock_z3n' vulnerability without requiring any signup.
