Malicious Code Injection in burning_bear_z3n: A Threat to npm Packages
Summary
MAL-2025-93451: Malicious code in burning_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 'burning_bear_z3n' package is part of the npm ecosystem, which is widely used for JavaScript package management. This package was identified as part of a malicious campaign that aimed to exploit the npm registry by flooding it with derivative packages. The malicious nature of this package lies in its ability to modify critical files and republish itself under various names, thereby compromising the integrity of the npm ecosystem.
Vulnerability Detail
The vulnerability in 'burning_bear_z3n' originates from its association with the tea.xyz token reward campaign. This package contains scripts designed to automatically generate and publish derivative packages with randomized names, which can inflate developer reputation scores. The malicious payload alters the package.json file by removing private flags, changing version numbers, and continuously republishing variants, leading to pollution of the npm registry and potential security risks for developers relying on these packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall burning_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, consider using a package-lock.json file to lock your dependencies to known safe versions. This can prevent the installation of the malicious package until a fix is applied. You can also monitor your dependencies using tools like Vulert, which alerts you to vulnerabilities in real-time.
Conclusion
The 'burning_bear_z3n' package poses a significant risk due to its malicious nature and the potential for widespread impact on the npm ecosystem. It is crucial for developers to take immediate action to remove this package and monitor their dependencies for vulnerabilities. Utilizing tools like Vulert can enhance your security posture by providing real-time alerts.
See every vulnerability recorded for burning_bear_z3n →
FAQ
The 'burning_bear_z3n' package is an npm package that has been identified as part of a malicious campaign to exploit the npm registry.
This vulnerability can lead to the pollution of the npm registry and may compromise the security of your project by introducing malicious code.
You should uninstall the 'burning_bear_z3n' package immediately and monitor your dependencies for any further vulnerabilities.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.
Vulert monitors and alerts for open-source vulnerabilities in your software using just the package-lock.json file, providing real-time insights into potential threats.
