Malicious Code Injection in future_gerbil_z3n Package
Summary
MAL-2025-94647: Malicious code in future_gerbil_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 future_gerbil_z3n package is part of the npm ecosystem, often associated with token reward campaigns. It is designed to facilitate the generation and publication of derivative packages. However, this package has been identified as containing malicious code that compromises its integrity and the security of applications that depend on it.
Vulnerability Detail
The vulnerability stems from the malicious code embedded within the future_gerbil_z3n package, which is part of a broader trend of npm packages that aim to inflate developer reputation scores through deceptive practices. The code modifies the package.json file to remove private flags, alters version numbers, and generates random package names, leading to the continuous republishing of these variants. This not only pollutes the npm registry but also poses a risk to developers who may unknowingly integrate these compromised packages into their projects.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall future_gerbil_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 future_gerbil_z3n package and look for alternative packages that provide similar functionality without the associated risks. Additionally, consider using tools like Vulert to monitor your package-lock.json for vulnerabilities.
Conclusion
The future_gerbil_z3n package contains malicious code that poses significant risks to developers and their applications. It is crucial to remove this package and monitor your projects for vulnerabilities. Utilizing tools like Vulert can help maintain the security of your software.
See every vulnerability recorded for future_gerbil_z3n →
FAQ
It is an npm package associated with token reward campaigns, designed to generate and publish derivative packages.
The malicious code can modify your package.json, remove private flags, and lead to the republishing of compromised packages, potentially affecting your application's security.
You should uninstall the future_gerbil_z3n package immediately and check for any alternative packages that can fulfill your requirements.
Yes, you can use Vulert, which monitors your package-lock.json for vulnerabilities in real-time without requiring code access or installation.
You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.
