Malicious Code Injection in fluttering_haddock_z3n: A Threat to npm Packages
Summary
MAL-2025-102832: Malicious code in fluttering_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
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
Background
The package fluttering_haddock_z3n 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 scripts that compromise the integrity of the npm registry.
Vulnerability Detail
The vulnerability in fluttering_haddock_z3n originates from its inclusion in a campaign that floods the npm registry with malicious packages. The malicious payload modifies the package.json file by removing private flags, altering version numbers, and generating random package names. This behavior leads to the continuous republishing of variants, which pollutes the npm registry and can potentially harm developers relying on legitimate packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall fluttering_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 fluttering_haddock_z3n package from your project by executing: npm uninstall fluttering_haddock_z3n. This will prevent any malicious scripts from executing until a secure version is available.
Conclusion
The fluttering_haddock_z3n package poses a significant risk due to its malicious code that modifies package.json and floods the npm registry. It is crucial to take immediate action by updating or removing the package and utilizing tools like Vulert for ongoing monitoring.
See every vulnerability recorded for fluttering_haddock_z3n →
FAQ
fluttering_haddock_z3n is an npm package that has been linked to a malicious campaign aimed at inflating developer reputation scores through the automatic generation of derivative packages.
The vulnerability can lead to the pollution of the npm registry, potentially causing conflicts with legitimate packages and compromising the integrity of your project.
If you have installed fluttering_haddock_z3n, it is recommended to uninstall it immediately and monitor for any updates or patches from the package maintainers.
You can use Vulert, which monitors and alerts in real-time for open-source vulnerabilities using just your package-lock.json file. You can also check your application against known vulnerabilities using the Vulert playground without any signup.
To prevent future vulnerabilities, regularly audit your dependencies, keep your packages updated, and utilize tools like Vulert to monitor for any open-source vulnerabilities.
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
