Malicious Code Injection in balanced_rat_z3n Package - npm Vulnerability

balanced_rat_z3n Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-93347: Malicious code in balanced_rat_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 balanced_rat_z3n package is part of the npm ecosystem and appears to be associated with the tea.xyz token reward campaign. This package is designed to facilitate the automatic generation and publishing of derivative packages, which can inflate developer reputation scores in exchange for token rewards. Its functionality is compromised due to the presence of malicious scripts that manipulate package metadata.

Vulnerability Detail

The vulnerability in the balanced_rat_z3n package stems from its inclusion in a malicious campaign that floods the npm registry with derivative packages. The malicious code modifies the package.json file to remove private flags, alters version numbers, and generates random package names, leading to the pollution of the npm registry. This can result in developers unknowingly using compromised packages, which may introduce security risks and instability into their applications.

How To Fix

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

npm uninstall balanced_rat_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 workaround, you can avoid using the balanced_rat_z3n package altogether and look for alternative packages that provide similar functionality without the associated risks. Additionally, consider using the Vulert tool to monitor your package-lock.json file for vulnerabilities in real-time.

Conclusion

The balanced_rat_z3n package poses a significant security risk due to its malicious code that alters package metadata and floods the npm registry. It is essential to remove this package from your project and utilize tools like Vulert to monitor for vulnerabilities in your dependencies.

See every vulnerability recorded for balanced_rat_z3n →

Share this vulnerability

FAQ

The balanced_rat_z3n package is an npm package that is part of a malicious campaign aimed at inflating developer reputation scores through the automatic generation of derivative packages.

The vulnerability can lead to the introduction of malicious code into your application, potentially compromising its security and stability.

You should uninstall the balanced_rat_z3n package immediately using the command npm uninstall balanced_rat_z3n and monitor your dependencies for any other vulnerabilities.

Yes, Vulert allows you to monitor your package-lock.json file for open-source vulnerabilities in real-time without requiring code access or installation.

There is no patch for the balanced_rat_z3n package due to its malicious nature. The best course of action is to remove it from your project.

How To Fix

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

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