Malicious Code Injection in gradual_bear_z3n: npm Package Vulnerability
Summary
MAL-2025-103330: Malicious code in gradual_bear_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 gradual_bear_z3n package is part of the npm ecosystem, which is widely used for JavaScript package management. This package has been identified as part of a malicious campaign aimed at exploiting npm's publishing capabilities. It is designed to generate and publish derivative packages with randomized names, which can lead to reputation inflation for the perpetrators involved in the tea.xyz token reward scheme.
Vulnerability Detail
The vulnerability originates from the malicious code embedded within the gradual_bear_z3n package. This code modifies the package.json file to remove private flags, alters version numbers, and generates random package names, effectively polluting the npm registry. The implications of this vulnerability include potential security risks for developers who unknowingly use these compromised packages, as well as the degradation of the npm ecosystem's integrity.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall gradual_bear_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 gradual_bear_z3n package and monitor your dependencies for any signs of this malicious package. Additionally, consider using tools like Vulert to monitor your package-lock.json for vulnerabilities.
Conclusion
The gradual_bear_z3n package poses a significant risk due to its malicious code that alters package metadata and floods the npm registry with compromised packages. It is crucial for developers to remove this package and utilize monitoring tools like Vulert to safeguard their applications from similar vulnerabilities.
See every vulnerability recorded for gradual_bear_z3n →
FAQ
It is an npm package that has been identified as part of a malicious campaign to exploit the npm registry.
If you are using the gradual_bear_z3n package, your project may be at risk of security breaches and could contribute to the pollution of the npm registry.
You should uninstall the gradual_bear_z3n package immediately and monitor your dependencies for any related issues.
Yes, you can use the Vulert playground to check your application for vulnerabilities without needing to sign up.
Regularly audit your dependencies, use tools like Vulert for real-time monitoring, and stay informed about known vulnerabilities in the npm ecosystem.
