Malicious Code Injection in dear_halibut_z3n: A Threat to npm Packages
Summary
MAL-2025-93931: Malicious code in dear_halibut_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 dear_halibut_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 scripts, making them a significant threat to the integrity of the npm ecosystem.
Vulnerability Detail
The vulnerability in dear_halibut_z3n stems from its association with a malicious campaign that modifies package.json files to remove private flags, alters version numbers, and generates random package names. This behavior not only compromises the security of the affected packages but also pollutes the npm registry, making it difficult for developers to trust the packages they use. The malicious payload is designed to continuously republish variants, exacerbating the issue and potentially leading to further exploitation.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall dear_halibut_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 manually remove the dear_halibut_z3n package from your project by executing the following command: npm uninstall dear_halibut_z3n. Additionally, ensure that your package-lock.json file is monitored for any unauthorized changes.
Conclusion
The dear_halibut_z3n package poses a significant security risk due to its malicious behavior. It is essential for developers to be vigilant and take immediate action to protect their projects by updating or removing the affected package. Utilizing tools like Vulert can aid in monitoring for such vulnerabilities effectively.
See every vulnerability recorded for dear_halibut_z3n →
FAQ
dear_halibut_z3n is an npm package that has been identified as part of a malicious campaign targeting the npm registry.
The vulnerability can lead to unauthorized modifications of your package.json file and the introduction of malicious code into your project.
You should update the package to a patched version if available or uninstall it to prevent potential security risks.
You can use tools like Vulert, which monitors your package-lock.json for open-source vulnerabilities in real-time without requiring code access.
You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.
