Malicious Code Exploit in dynamic_bat_z3n Package: npm Vulnerability Overview
Summary
MAL-2025-94149: Malicious code in dynamic_bat_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 dynamic_bat_z3n package is part of the npm ecosystem, primarily used for JavaScript development. It has been identified as part of a broader malicious campaign associated with the tea.xyz token reward initiative. This campaign has led to the proliferation of numerous packages that contain scripts designed to manipulate the npm registry, thereby compromising the integrity of the ecosystem.
Vulnerability Detail
The vulnerability in the dynamic_bat_z3n package stems from its inclusion in a malicious campaign that modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior is intended to inflate developer reputation scores for token rewards, leading to the continuous republishing of variants that pollute the npm registry. The origin of this issue is linked to the tea.xyz token reward campaign, which has flooded npm with similar malicious packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall dynamic_bat_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 the following command to uninstall it: npm uninstall dynamic_bat_z3n. Additionally, consider using npm audit to identify and address other potential vulnerabilities in your project.
Conclusion
The dynamic_bat_z3n package poses a significant risk due to its malicious behavior aimed at manipulating the npm registry. It is crucial for developers to be vigilant and take immediate action to remove this package and monitor their projects for vulnerabilities. Utilizing tools like Vulert can help maintain the security of your applications.
See every vulnerability recorded for dynamic_bat_z3n →
FAQ
dynamic_bat_z3n is an npm package that has been identified as part of a malicious campaign aimed at manipulating the npm registry.
This vulnerability can lead to the pollution of the npm registry and may compromise the integrity of your project by introducing malicious code.
You should uninstall the dynamic_bat_z3n package immediately and monitor your project for any other vulnerabilities.
You can use tools like Vulert, which monitors your package-lock.json file to alert you in real-time for open-source vulnerabilities.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected without needing to sign up.
