Malicious Code Injection in statistical_gerbil_z3n Package

statistical_gerbil_z3n Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-96762: Malicious code in statistical_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

The statistical_gerbil_z3n package is part of the npm ecosystem, typically used for various statistical computations and data analysis tasks. However, this package has been identified as part of a malicious campaign that aims to inflate developer reputation scores through the automatic generation and publication of derivative packages. The presence of malicious scripts within this package poses significant risks to developers and their projects.

Vulnerability Detail

The vulnerability originates from the malicious code embedded in the statistical_gerbil_z3n package, which is linked to the tea.xyz token reward campaign. This code includes autopublish scripts that modify the package.json file by removing private flags, altering version numbers, and generating random package names. The continuous republishing of these variants pollutes the npm registry, potentially leading to reputation damage for developers and security risks for users who inadvertently install these compromised packages.

How To Fix

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

npm uninstall statistical_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 remove the statistical_gerbil_z3n package from your project by executing the command: 'npm uninstall statistical_gerbil_z3n'. Additionally, consider using alternative packages that provide similar functionality without the associated risks.

Conclusion

The statistical_gerbil_z3n package has been identified as containing malicious code that poses significant risks to developers and their projects. It is essential to take immediate action by updating or removing the package and utilizing tools like Vulert for ongoing monitoring of vulnerabilities.

See every vulnerability recorded for statistical_gerbil_z3n →

Share this vulnerability

FAQ

It is an npm package used for statistical computations but has been compromised with malicious code.

The malicious code can modify your package.json, inflate reputation scores, and pollute the npm registry, leading to potential security risks.

You should uninstall the package immediately and check for any updates or patches that may address the vulnerability.

Yes, you can use tools like Vulert, which monitors your package-lock.json for open-source vulnerabilities in real-time.

Yes, you can use the Vulert playground at Vulert Scanner to check for vulnerabilities in your application without any signup.

How To Fix

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

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