Malicious Code Injection in changing_gopher_z3n Package
Summary
MAL-2025-100323: Malicious code in changing_gopher_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 changing_gopher_z3n package is part of the npm ecosystem, which is widely used for JavaScript package management. This package is associated with the tea.xyz token reward campaign, which has been known to flood the npm registry with malicious packages. These packages often contain scripts designed to manipulate package metadata and inflate developer reputation scores for token rewards.
Vulnerability Detail
The vulnerability in the changing_gopher_z3n package stems from its inclusion in a campaign that deploys malicious scripts. These scripts modify the package.json file to remove private flags, alter version numbers, and generate random package names, leading to the continuous republishing of these variants. This behavior not only pollutes the npm registry but also poses a risk to developers who may unknowingly install these compromised packages, potentially leading to further exploitation.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall changing_gopher_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 prevent the installation of the changing_gopher_z3n package by using the following command to uninstall it: npm uninstall changing_gopher_z3n. Additionally, monitor your package-lock.json file for any unauthorized changes.
Conclusion
The changing_gopher_z3n package has been identified as a malicious entity within the npm ecosystem, posing significant risks to developers and their applications. It is crucial to take immediate action to mitigate these risks by updating or removing the package and utilizing monitoring tools like Vulert to maintain the security of your projects.
See every vulnerability recorded for changing_gopher_z3n →
FAQ
The changing_gopher_z3n package is an npm package that has been identified as part of a malicious campaign aimed at manipulating npm registry data.
This vulnerability can lead to the installation of compromised packages, which may introduce security risks or instability in your application.
If you have installed the changing_gopher_z3n package, it is advisable to uninstall it immediately and check for any unauthorized changes in your project.
Yes, you can use tools like Vulert, which monitors your package-lock.json file for open-source vulnerabilities in real-time. You can also check your application against known vulnerabilities using the Vulert playground.
Regularly update your dependencies, use tools like Vulert for monitoring, and review your package-lock.json file for any suspicious changes.
