Malicious Code Injection in determined_bat_z3n Package - npm Vulnerability

determined_bat_z3n Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-101376: Malicious code in determined_bat_z3n (npm). Affected versions are not published. No fix is published. How to fix ↓

Free scan

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.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The determined_bat_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, its functionality is compromised by malicious code that alters package metadata.

Vulnerability Detail

The vulnerability originates from the determined_bat_z3n package, which contains malicious scripts that modify the package.json file. These scripts remove private flags, change version numbers, and generate random package names, leading to the continuous republishing of variants that pollute the npm registry. This can result in significant reputational damage for developers and can compromise the integrity of the npm ecosystem.

How To Fix

This package is malicious. Remove it and rotate any credentials it could have accessed.

npm uninstall determined_bat_z3n

If 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 remove the determined_bat_z3n package from your project by executing 'npm uninstall determined_bat_z3n'. This will prevent the execution of any malicious scripts associated with this package.

Conclusion

The determined_bat_z3n package poses a significant risk due to its malicious code that alters package metadata. It is crucial to take immediate action by updating or removing the package to safeguard your project and maintain the integrity of the npm ecosystem.

See every vulnerability recorded for determined_bat_z3n →

Share this vulnerability

FAQ

The determined_bat_z3n package is an npm package that is part of a token reward campaign, designed to automatically publish derivative packages.

The vulnerability can lead to the modification of your package.json file, potentially compromising your project's integrity and reputation.

You should uninstall the determined_bat_z3n package immediately and check for any unauthorized changes to your package.json file.

Yes, you can use Vulert, which monitors and alerts for open-source vulnerabilities in your software using just package-lock.json. You can check your application for vulnerabilities using the Vulert playground without any signup.

Regularly audit your dependencies and use tools like Vulert to monitor for vulnerabilities in real-time.

How To Fix

This package is malicious. Remove it and rotate any credentials it could have accessed.

npm uninstall determined_bat_z3n

If 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 →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback