Malicious Code Injection in deep_bat_z3n: A Threat to npm Ecosystem
Summary
MAL-2025-101254: Malicious code in deep_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 package 'deep_bat_z3n' is part of a broader campaign targeting the npm ecosystem, specifically associated with the tea.xyz token reward initiative. This package, like others in the campaign, is designed to manipulate npm's package registry by generating and publishing numerous derivative packages with randomized names. Its functionality is compromised due to the presence of malicious scripts that aim to inflate developer reputation scores for token rewards.
Vulnerability Detail
The vulnerability in 'deep_bat_z3n' originates from its inclusion in a malicious campaign that floods the npm registry with derivative packages. The malicious payload modifies the package.json file by removing private flags, altering version numbers, and generating random package names. This behavior not only pollutes the npm registry but also poses a risk of reputation damage to developers and potential security threats to applications relying on these packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall deep_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 avoid using 'deep_bat_z3n' and any packages that depend on it. Additionally, consider using npm audit to identify and address vulnerabilities in your project dependencies.
Conclusion
The 'deep_bat_z3n' package poses a significant threat to the npm ecosystem due to its malicious behavior aimed at inflating developer reputation scores. It is essential to remove this package and monitor your dependencies for vulnerabilities to maintain the security of your applications.
See every vulnerability recorded for deep_bat_z3n →
FAQ
The vulnerability involves malicious code that modifies package.json files and floods the npm registry with derivative packages.
You can use Vulert to monitor and alert for open-source vulnerabilities in your software. Visit Vulert Scanner to check your application without any signup.
Using deep_bat_z3n can lead to reputation damage for developers and potential security threats due to the pollution of the npm registry.
Regularly audit your dependencies using tools like npm audit and stay informed about vulnerabilities in the packages you use.
Remove the package immediately and check for any other affected packages. Update your dependencies to secure versions.
