Malicious Code Vulnerability in direct_goose_z3n Package
Summary
MAL-2025-101587: Malicious code in direct_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 direct_goose_z3n package 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 code that compromises its integrity and the security of the npm registry.
Vulnerability Detail
The vulnerability in the direct_goose_z3n package stems from its malicious payload, which modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior leads to the continuous republishing of variants, polluting the npm registry and potentially affecting other packages and developers. The origin of this issue is linked to the broader trend of malicious packages flooding the npm ecosystem, specifically targeting the tea protocol token rewards.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall direct_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 remove the direct_goose_z3n package from your project by executing the following command: npm uninstall direct_goose_z3n. This will prevent any malicious code from executing until a secure version is available.
Conclusion
The direct_goose_z3n package has been identified as containing malicious code that poses a significant risk to developers and the npm ecosystem. It is crucial to take immediate action by updating or uninstalling the package to mitigate potential threats. Utilizing tools like Vulert can help monitor and manage vulnerabilities effectively.
See every vulnerability recorded for direct_goose_z3n →
FAQ
The direct_goose_z3n package is an npm package associated with the tea.xyz token reward campaign, designed to generate and publish derivative packages.
The vulnerability modifies the package.json file, removes private flags, changes version numbers, and generates random package names, leading to pollution of the npm registry.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. By using the Vulert playground, you can check if your application is affected without any signup.
If you cannot update the package, consider uninstalling it as a temporary measure to prevent any potential exploitation of the vulnerability.
You can visit the Vulert website for real-time monitoring and alerts on open-source vulnerabilities, as well as access detailed information on specific vulnerabilities.
