Malicious Code Injection in comparative_goose_z3n: A Threat to npm Ecosystem
Summary
MAL-2025-100746: Malicious code in comparative_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
comparative_goose_z3n is an npm package that has been identified as part of a malicious campaign targeting the npm registry. This package is associated with the tea.xyz token reward initiative, which has been known to flood the npm ecosystem with harmful packages. The primary function of this package is to manipulate the npm registry by generating and publishing derivative packages with altered metadata, thereby inflating developer reputation scores for token rewards.
Vulnerability Detail
The vulnerability in comparative_goose_z3n originates from its design to include malicious scripts that automatically modify the package.json file. These modifications remove private flags, alter version numbers, and create random package names, contributing to the pollution of the npm registry. The malicious payload can lead to severe ramifications, including the potential for developers to unknowingly use compromised packages, which can introduce security risks and undermine the integrity of the npm ecosystem.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall comparative_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 workaround, you can avoid using the comparative_goose_z3n package and replace its functionality with a trusted alternative. Additionally, regularly audit your npm packages using tools like npm audit to identify and mitigate potential vulnerabilities.
Conclusion
The comparative_goose_z3n package poses a significant threat to the npm ecosystem due to its malicious code designed to manipulate package metadata. It is crucial for developers to remove this package from their projects and stay vigilant by monitoring their dependencies for any vulnerabilities.
See every vulnerability recorded for comparative_goose_z3n →
FAQ
The malicious code is designed to modify package metadata, remove private flags, and publish variants of the package to inflate developer reputation scores.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software. By checking your package-lock.json file, you can determine if your application is affected.
Using compromised packages can lead to security vulnerabilities, data breaches, and potential exploitation of your application by malicious actors.
There is no patch available for this specific package. The recommended action is to uninstall it and remove any references from your project.
Regularly audit your dependencies, use trusted sources for packages, and consider using tools like Vulert to monitor for vulnerabilities in real-time.
