Malicious Code Injection in classical_gerbil_z3n: A Threat to npm Packages
Summary
MAL-2025-93572: Malicious code in classical_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 package classical_gerbil_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 linked to a series of malicious activities aimed at inflating developer reputation scores. The package's functionality is compromised by malicious scripts that manipulate its metadata and behavior.
Vulnerability Detail
The vulnerability in classical_gerbil_z3n stems from its inclusion in a campaign that floods the npm registry with derivative packages. These packages contain scripts that modify the package.json file to remove private flags, alter version numbers, and generate random package names. This behavior not only pollutes the npm registry but also poses a risk to developers who may unknowingly use these compromised packages, leading to potential security breaches and loss of trust in the npm ecosystem.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall classical_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 measure, you can avoid using the classical_gerbil_z3n package and monitor your project for any dependencies that may indirectly include it. Additionally, consider using tools like Vulert to monitor your package-lock.json for vulnerabilities. You can check if your application is affected by this vulnerability using the Vulert playground at https://vulert.com/scanner without any signup.
Conclusion
The classical_gerbil_z3n package poses a significant risk due to its malicious code injection. It is essential to remove this package from your project and stay vigilant by using monitoring tools like Vulert to ensure the security of your applications.
See every vulnerability recorded for classical_gerbil_z3n →
FAQ
classical_gerbil_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 introduction of malicious code into your project, potentially compromising security and functionality.
You should remove the classical_gerbil_z3n package from your project and monitor for any dependencies that may include it.
Yes, tools like Vulert can help monitor your package-lock.json for vulnerabilities in real-time.
You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.
