Malicious Code Injection in neat_gerbil_z3n: A Threat to npm Packages

neat_gerbil_z3n Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-106233: Malicious code in neat_gerbil_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

neat_gerbil_z3n is an npm package that is part of the tea.xyz token reward campaign. This package is designed to interact with the npm ecosystem, potentially providing functionalities related to token rewards. However, it has been identified as a malicious package that can compromise the integrity of the npm registry and the applications that depend on it.

Vulnerability Detail

The vulnerability in neat_gerbil_z3n stems from its malicious code that modifies the package.json file of the project. This code removes private flags, alters version numbers, and generates random package names, leading to the automatic publication of derivative packages. The origin of this issue is linked to the tea.xyz token reward campaign, which aims to inflate developer reputation scores by flooding the npm registry with these malicious packages. The ramifications include the potential for developers to unknowingly install compromised packages, leading to security risks and pollution of the npm registry.

How To Fix

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

npm uninstall neat_gerbil_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 neat_gerbil_z3n package and replace it with a trusted alternative. Always verify the integrity of packages before installation.

Conclusion

The neat_gerbil_z3n package poses a significant risk due to its malicious code that alters project files and floods the npm registry. It is crucial for developers to be vigilant and remove such packages from their projects. Regular monitoring and updates are essential to maintain the security of your applications.

See every vulnerability recorded for neat_gerbil_z3n →

Share this vulnerability

FAQ

neat_gerbil_z3n is an npm package associated with the tea.xyz token reward campaign, which has been identified as containing malicious code.

The vulnerability can lead to the installation of compromised packages, which may alter your project's dependencies and introduce security risks.

You should uninstall the package immediately using the command npm uninstall neat_gerbil_z3n and check your project for any other compromised packages.

You can use Vulert, which monitors and alerts you in real-time for open-source vulnerabilities in your software by analyzing your package-lock.json file.

Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.

How To Fix

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

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