Malicious Code Injection in simple_gibbon_z3n: A Threat to npm Ecosystem
Summary
MAL-2025-90504: Malicious code in simple_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 package 'simple_gibbon_z3n' 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 through automated publishing of derivative packages.
Vulnerability Detail
The vulnerability in 'simple_gibbon_z3n' originates from its malicious intent to modify the package.json file by removing private flags and changing version numbers. It generates random package names, often themed around Indonesian culture, and continuously republishes these variants to pollute the npm registry. This not only compromises the integrity of the npm ecosystem but also poses risks to developers who may unknowingly use these packages, leading to potential security breaches in their applications.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall simple_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, avoid using the 'simple_gibbon_z3n' package and monitor your project for any dependencies that may inadvertently include it. Regularly audit your package-lock.json file for any signs of malicious packages.
Conclusion
The 'simple_gibbon_z3n' package poses a significant threat to the npm ecosystem due to its malicious code designed to manipulate package metadata. It is crucial for developers to be vigilant and remove any instances of this package from their projects. Utilizing tools like Vulert can help in monitoring for such vulnerabilities effectively.
See every vulnerability recorded for simple_gibbon_z3n →
FAQ
It is an npm package that has been identified as part of a malicious campaign to manipulate the npm registry and inflate developer reputation scores.
Using this package can lead to security breaches, as it modifies critical metadata and can introduce other malicious packages into your project.
You should uninstall the package immediately using 'npm uninstall simple_gibbon_z3n' and check for any dependencies that may be affected.
You can use tools like Vulert, which monitors your package-lock.json file for open-source vulnerabilities in real-time without requiring code access or installation.
Yes, you can use the Vulert playground at Vulert Scanner to check for vulnerabilities in your application without needing to sign up.
