Malicious Code Injection in basic_ferret_z3n Package

basic_ferret_z3n Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-93356: Malicious code in basic_ferret_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 Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The basic_ferret_z3n package is part of the npm ecosystem, primarily used for various JavaScript applications. It is associated with the tea.xyz token reward campaign, which has been known to flood the npm registry with packages that inflate developer reputation scores. This package, like others in the campaign, contains scripts designed to automatically generate and publish derivative packages, leading to potential misuse and pollution of the npm registry.

Vulnerability Detail

The vulnerability in the basic_ferret_z3n package stems from its malicious payload, which modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior is intended to continuously republish variants, thereby polluting the npm registry and compromising the integrity of the ecosystem. The origin of this vulnerability is linked to the tea.xyz token reward campaign, which employs such tactics to manipulate developer reputation scores.

How To Fix

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

npm uninstall basic_ferret_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 basic_ferret_z3n package from your project by executing the following command: npm uninstall basic_ferret_z3n. This will prevent any malicious activity associated with the package until a secure version is available.

Conclusion

The basic_ferret_z3n package contains a serious vulnerability that can lead to malicious code injection and pollution of the npm registry. It is crucial to take immediate action by updating or removing the package to protect your applications from potential risks.

See every vulnerability recorded for basic_ferret_z3n →

Share this vulnerability

FAQ

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

The vulnerability can lead to the pollution of the npm registry, potentially compromising the integrity of your application and exposing it to further security risks.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software. By utilizing the Vulert playground, you can check if your application is affected by this vulnerability without any signup.

If an immediate update is not possible, consider removing the package from your project as a temporary measure to mitigate the risk.

More information can be found in the vulnerability details provided by the Amazon Inspector and on platforms that track open-source vulnerabilities.

How To Fix

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

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