Malicious Code Injection in dirty_bear_z3n Package: A Threat to npm Ecosystem
Summary
MAL-2025-101594: Malicious code in dirty_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 dirty_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 that aims to exploit the npm registry by generating and publishing numerous derivative packages with randomized names. These actions are intended to inflate developer reputation scores for token rewards associated with the tea.xyz protocol.
Vulnerability Detail
The vulnerability in the dirty_bear_z3n package stems from its malicious code that 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, which pollutes the npm registry and can compromise the integrity of the ecosystem. The origin of this vulnerability is linked to the tea.xyz token reward campaign, which has been flooding the npm registry with such malicious packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall dirty_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 malicious package by using npm's package-lock.json file to monitor dependencies. Ensure that your package-lock.json does not include dirty_bear_z3n. You can also use tools like Vulert to monitor your project for vulnerabilities without needing to access the code directly.
Conclusion
The dirty_bear_z3n package poses a significant threat to the npm ecosystem due to its malicious code that alters package metadata and floods the registry with derivative packages. It is essential for developers to be vigilant and remove this package from their projects to maintain the integrity of their applications.
See every vulnerability recorded for dirty_bear_z3n →
FAQ
The dirty_bear_z3n package is an npm package that has been identified as part of a malicious campaign to exploit the npm registry.
The malicious code modifies your package.json file, removes private flags, and generates random package names, which can lead to pollution of the npm registry and potential security risks.
You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.
If you have installed the dirty_bear_z3n package, you should uninstall it immediately using 'npm uninstall dirty_bear_z3n' and check for any dependencies that may rely on it.
Currently, there is no patch for the dirty_bear_z3n package. The best course of action is to remove the package and monitor your project for any vulnerabilities.
