Malicious Code Injection in separate_bear_z3n Package - npm Vulnerability
Summary
MAL-2025-108550: Malicious code in separate_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 separate_bear_z3n package is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to facilitate the automatic generation and publication of derivative packages, which can inflate developer reputation scores for token rewards. However, it has been identified as containing malicious code that compromises its integrity and the security of the npm registry.
Vulnerability Detail
The vulnerability originates from the package's malicious payload, which modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior leads to the continuous republishing of variants, polluting the npm registry and potentially affecting other developers and users relying on legitimate packages. The malicious scripts (auto.js, autopublish.js, etc.) are designed to automate this process, making it difficult to track and mitigate the impact.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall separate_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 workaround, you can prevent the installation of this package by using npm's package-lock.json file to lock your dependencies. Additionally, you can monitor your project for vulnerabilities using tools like Vulert, which can alert you to any open-source vulnerabilities in real-time.
Conclusion
The separate_bear_z3n package has been identified as containing malicious code that poses a significant risk to the npm ecosystem. It is crucial for developers to remove this package and monitor their projects for vulnerabilities to maintain security and integrity.
See every vulnerability recorded for separate_bear_z3n →
FAQ
The separate_bear_z3n package is an npm package associated with the tea.xyz token reward campaign, designed to automate the generation and publication of derivative packages.
The vulnerability can lead to the pollution of the npm registry, potentially affecting other packages and developers. It compromises the integrity of your dependencies.
You should remove the separate_bear_z3n package from your project immediately and monitor for any updates or patches.
Yes, you can use the Vulert playground to check if your application is affected by this vulnerability without needing to sign up.
Regularly monitor your dependencies using tools like Vulert, and keep your packages updated to their latest secure versions.
