Malicious Code Injection in working_goose_z3n: A Threat to npm Packages
Summary
MAL-2025-97405: Malicious code in working_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
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 'working_goose_z3n' package is part of the npm ecosystem, which is widely used for JavaScript package management. This package, like many others, is intended to facilitate the development and deployment of applications by providing reusable code modules. However, it has been identified as part of a malicious campaign that exploits npm's publishing system, leading to significant security concerns.
Vulnerability Detail
The vulnerability stems from malicious code embedded within the 'working_goose_z3n' package. This package is associated with the tea.xyz token reward campaign, which aims to inflate developer reputation scores through the automatic generation and publication of derivative packages. The malicious payload modifies the package.json file by removing private flags, altering version numbers, and generating random package names, which can lead to pollution of the npm registry and potential exploitation of applications that depend on these packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall working_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 'working_goose_z3n' package from your project by executing the command: 'npm uninstall working_goose_z3n'. This will prevent any potential exploitation until a secure version is available.
Conclusion
The 'working_goose_z3n' package presents a significant security risk due to its malicious code that alters package metadata and publishes unauthorized derivatives. It is essential to take immediate action by updating or removing the package to safeguard your applications. Utilizing tools like Vulert can help maintain awareness of vulnerabilities in your dependencies.
See every vulnerability recorded for working_goose_z3n →
FAQ
The vulnerability involves malicious code that modifies package.json files and publishes derivative packages to inflate developer reputation scores.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check your application without any signup.
If an immediate update is not possible, consider uninstalling the package as a temporary measure to mitigate risks.
While specific exploits may not be publicly documented, the nature of the vulnerability poses a risk of package pollution and potential exploitation of dependent applications.
Regularly audit your dependencies, use tools like Vulert for monitoring, and stay updated with security advisories related to the packages you use.
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
