Malicious Code Injection in supposed_gibbon_z3n Package
Summary
MAL-2025-96881: Malicious code in supposed_gibbon_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 supposed_gibbon_z3n package is part of a series of npm packages that emerged during the tea.xyz token reward campaign. These packages are designed to inflate developer reputation scores by automatically generating and publishing derivative packages with randomized names. However, they contain malicious scripts that compromise the integrity of the npm registry.
Vulnerability Detail
The vulnerability in the supposed_gibbon_z3n package stems from its inclusion in a malicious campaign that 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 allowing for further exploitation by malicious actors. The origin of this vulnerability is linked to the automated scripts (auto.js, autopublish.js, etc.) that are part of the package, which are designed to manipulate the npm ecosystem for token rewards.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall supposed_gibbon_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 workaround, you can temporarily remove the package from your project by running the command: npm uninstall supposed_gibbon_z3n. This will prevent any malicious code from executing while you assess the impact on your application.
Conclusion
The supposed_gibbon_z3n package is a malicious npm package that poses significant risks to developers and their applications. Immediate action is required to remove this package and prevent further exploitation. Utilizing tools like Vulert can help in monitoring and managing vulnerabilities effectively.
See every vulnerability recorded for supposed_gibbon_z3n →
FAQ
The supposed_gibbon_z3n package is an npm package that is part of a malicious campaign aimed at inflating developer reputation scores through automated publishing of derivative packages.
This vulnerability can lead to the pollution of the npm registry and may expose your application to further security risks if the malicious code is executed.
You should immediately uninstall the supposed_gibbon_z3n package and monitor your application for any unusual behavior.
Yes, you can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time using just your package-lock.json file. You can check your application against known vulnerabilities using the Vulert playground.
Regularly audit your dependencies, keep them updated, and utilize tools like Vulert to monitor for vulnerabilities in real-time.
