Malicious Code Detected in left_gibbon_z3n: npm Package Vulnerability
Summary
MAL-2025-95206: Malicious code in left_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 left_gibbon_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 sharing of JavaScript libraries and tools. However, it has been identified as part of a malicious campaign that exploits npm's publishing mechanisms to inflate developer reputation scores through the creation of derivative packages.
Vulnerability Detail
The vulnerability in left_gibbon_z3n stems from its association with 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 these modified packages, which can pollute the npm registry and potentially compromise the integrity of applications relying on these packages. The malicious code is designed to automate the generation and publication of these packages, making it difficult for developers to track and manage their dependencies effectively.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall left_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 temporary workaround, you can avoid using the left_gibbon_z3n package altogether and look for alternative packages that provide similar functionality without the associated risks. Additionally, you can monitor your dependencies using tools like Vulert, which can alert you to vulnerabilities in real-time based on your package-lock.json file.
Conclusion
The left_gibbon_z3n package poses a significant risk due to its malicious code designed to manipulate npm's publishing system. It is crucial for developers to remove this package from their projects and monitor their dependencies for vulnerabilities. Utilizing tools like Vulert can provide additional security by alerting you to potential threats in real-time.
See every vulnerability recorded for left_gibbon_z3n →
FAQ
left_gibbon_z3n is an npm package that has been identified as part of a malicious campaign to inflate developer reputation scores.
The vulnerability can lead to the pollution of the npm registry, potentially compromising the integrity of your application's dependencies.
You should uninstall the package immediately using 'npm uninstall left_gibbon_z3n' and check your package-lock.json for any references to it.
Yes, tools like Vulert can monitor your package-lock.json file for vulnerabilities and alert you in real-time.
You can use the Vulert playground at Vulert Scanner to check if your application is affected without needing to sign up.
