Malicious Code Vulnerability in indirect_haddock_z3n Package
Summary
MAL-2025-104157: Malicious code in indirect_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 indirect_haddock_z3n package 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 the npm registry by flooding it with derivative packages. These packages are designed to inflate developer reputation scores through automated publishing scripts, which can lead to significant pollution of the npm registry.
Vulnerability Detail
The vulnerability in the indirect_haddock_z3n package stems from its malicious code that modifies the package.json file to remove private flags and changes version numbers. It generates random package names, primarily themed around Indonesian culture, and continuously republishes these variants. This behavior not only compromises the integrity of the npm registry but also poses risks to developers who may unknowingly use these tainted packages, potentially leading to security breaches and loss of trust in the ecosystem.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall indirect_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 measure, you can avoid using the indirect_haddock_z3n package and monitor your dependencies for any malicious activity. Regularly audit your npm packages using the command: npm audit, which will help identify vulnerabilities in your project.
Conclusion
The indirect_haddock_z3n package poses a significant risk due to its malicious behavior aimed at polluting the npm registry. It is crucial for developers to be vigilant about the packages they use and to take immediate action to remove any identified vulnerabilities. Utilizing tools like Vulert can aid in maintaining the security of your projects.
See every vulnerability recorded for indirect_haddock_z3n →
FAQ
It is an npm package that has been identified as part of a malicious campaign to flood the npm registry with derivative packages.
Using the indirect_haddock_z3n package can compromise your project's integrity and security, as it may introduce malicious code into your application.
You should uninstall the package immediately using the command: npm uninstall indirect_haddock_z3n.
You can use tools like Vulert, which monitors your package-lock.json file for open-source vulnerabilities in real-time. You can also check your application using the Vulert playground without any signup.
It is advisable to look for well-maintained and reputable packages that provide similar functionality without the associated risks.
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
