Malicious Code Injection in terrible_bear_z3n: A Threat to npm Packages
Summary
MAL-2025-91006: Malicious code in terrible_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
terrible_bear_z3n is an npm package that has been identified as part of a malicious campaign targeting the npm ecosystem. This package is associated with the tea.xyz token reward initiative, which has led to the proliferation of numerous derivative packages. These packages are designed to manipulate developer reputation scores by automatically generating and publishing variants with randomized names, thus compromising the integrity of the npm registry.
Vulnerability Detail
The vulnerability in terrible_bear_z3n stems from its inclusion in a malicious package campaign that modifies the package.json file to remove private flags and alters version numbers. It generates random package names, primarily themed around Indonesian culture, and continuously republishes these variants. This behavior not only pollutes the npm registry but also poses a risk to developers who may unknowingly use these compromised packages, potentially leading to 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 terrible_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 terrible_bear_z3n package and any other packages that are part of the tea.xyz token reward campaign. Monitor your project's dependencies closely and consider using tools like Vulert to identify vulnerabilities in your package-lock.json file.
Conclusion
The terrible_bear_z3n package poses a significant threat due to its malicious code designed to manipulate npm registry integrity. It is crucial for developers to remove this package and monitor their dependencies for vulnerabilities. Utilizing tools like Vulert can aid in maintaining a secure development environment.
See every vulnerability recorded for terrible_bear_z3n →
FAQ
The impact includes potential security breaches, pollution of the npm registry, and compromised developer reputation scores.
You can use Vulert to monitor your package-lock.json file for vulnerabilities. Visit Vulert Scanner to check your application without any signup.
You should uninstall the package immediately using the command 'npm uninstall terrible_bear_z3n' and review your other dependencies for security.
There are no patches available for terrible_bear_z3n, as it is recommended to remove the package entirely.
Regularly update your dependencies, use tools like Vulert for monitoring, and be cautious when installing packages from unverified sources.
