Malicious Code Injection in precise_goose_z3n: A Threat to npm Ecosystem
Summary
MAL-2025-107190: Malicious code in precise_goose_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 precise_goose_z3n is part of the npm ecosystem, which is widely used for JavaScript package management. It is often utilized by developers to manage dependencies in their projects. However, this package has been identified as part of a malicious campaign that aims to inflate developer reputation scores through the creation of numerous derivative packages with randomized names. This behavior not only compromises the integrity of the npm registry but also poses a significant risk to developers who may unknowingly incorporate these malicious packages into their applications.
Vulnerability Detail
The vulnerability in precise_goose_z3n stems from its association with a malicious campaign that modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This results in the continuous republishing of these variants, which pollutes the npm registry and can lead to security risks for developers who may inadvertently use these compromised packages. The malicious payload is designed to exploit the npm ecosystem by creating a false sense of legitimacy and inflating the reputation of the perpetrators.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall precise_goose_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 precise_goose_z3n package and instead look for alternative packages that provide similar functionality without the associated risks. Always verify the integrity and reputation of packages before including them in your project.
Conclusion
The precise_goose_z3n package poses a significant risk due to its malicious nature, which can compromise the integrity of your project and the npm ecosystem. It is crucial to remove this package and monitor your dependencies for vulnerabilities. Utilizing tools like Vulert can help you stay informed about potential threats in your software.
See every vulnerability recorded for precise_goose_z3n →
FAQ
precise_goose_z3n is an npm package that has been identified as part of a malicious campaign to inflate developer reputation scores through the creation of numerous derivative packages.
Using the precise_goose_z3n package can compromise your project's security by introducing malicious code that modifies your package.json and creates numerous unwanted packages.
You should uninstall the package immediately using the command npm uninstall precise_goose_z3n and review your project's dependencies for any other potentially malicious packages.
You can use tools like Vulert, which monitors your package-lock.json file to alert you in real-time for open-source vulnerabilities. You can check your application for vulnerabilities using the Vulert playground without any signup.
Yes, you should look for reputable packages that offer similar functionality. Always check the package's documentation and community feedback before integrating it into your project.
