Malicious Code Injection in compact_gibbon_z3n: A Threat to npm Packages
Summary
MAL-2025-100730: Malicious code in compact_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 'compact_gibbon_z3n' 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. The malicious nature of this package lies in its ability to modify critical files and republish itself, thereby polluting the npm registry.
Vulnerability Detail
The vulnerability originates from the package's malicious code, which includes scripts that alter the package.json file by removing private flags and changing version numbers. This behavior allows the package to generate random names and continuously republish variants, leading to a polluted npm registry. The ramifications include potential security risks for developers who unknowingly use these packages, as they may inadvertently compromise their applications by integrating malicious code.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall compact_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, developers should avoid using the 'compact_gibbon_z3n' package and monitor their dependencies for any similar malicious packages. Regularly auditing your npm packages can help identify and mitigate risks associated with such vulnerabilities.
Conclusion
The 'compact_gibbon_z3n' package poses a significant threat due to its malicious code that alters package files and repopulates the npm registry with harmful variants. It is essential for developers to remove this package and monitor their dependencies closely to maintain application security.
See every vulnerability recorded for compact_gibbon_z3n →
FAQ
It is an npm package that is part of a malicious campaign to inflate developer reputation scores by generating and publishing derivative packages.
If your application uses this package, it may inadvertently include malicious code that can compromise security and functionality.
You should uninstall the package immediately and check your package-lock.json for any references to it.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time using just your package-lock.json. You can check your application for vulnerabilities using the Vulert playground without any signup.
Yes, tools like Vulert can help identify vulnerabilities in your dependencies and provide alerts for any issues found.
