Malicious Code Injection in level_bat_z3n Package - npm Vulnerability

level_bat_z3n Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-105094: Malicious code in level_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 MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

The level_bat_z3n package is part of the npm ecosystem, often utilized in JavaScript applications. It is associated with the tea.xyz token reward campaign, which has been known to flood the npm registry with various packages. This package, like others in the campaign, is designed to manipulate the npm registry by generating and publishing derivative packages with randomized names, ultimately affecting the integrity of the ecosystem.

Vulnerability Detail

The vulnerability in the level_bat_z3n package stems from its malicious code that modifies the package.json file. This code removes private flags, alters version numbers, and generates random package names, which are then continuously republished to pollute the npm registry. The origin of this issue is linked to the tea.xyz token reward campaign, which incentivizes developers to inflate their reputation scores by creating numerous derivative packages. The ramifications include potential security risks for applications relying on this package, as well as the degradation of the npm registry's quality.

How To Fix

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

npm uninstall level_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 avoid using the level_bat_z3n package and look for alternative packages that provide similar functionality without the associated risks. Additionally, ensure that your package.json file is monitored for unauthorized changes.

Conclusion

The level_bat_z3n package presents a significant vulnerability due to its malicious code that alters package metadata and pollutes the npm registry. It is crucial for developers to remove this package from their projects and consider using monitoring tools like Vulert to safeguard against future vulnerabilities.

See every vulnerability recorded for level_bat_z3n →

Share this vulnerability

FAQ

The level_bat_z3n package is an npm package associated with the tea.xyz token reward campaign, known for flooding the npm registry with malicious packages.

The malicious code modifies your package.json file, potentially compromising your application's integrity and security by removing private flags and altering version numbers.

You should uninstall the level_bat_z3n package immediately using npm uninstall level_bat_z3n to mitigate any risks.

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

Regularly audit your dependencies, use tools like Vulert for monitoring, and stay informed about known vulnerabilities in the packages you use.

How To Fix

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

npm uninstall level_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