Malicious Code Injection in continuing_barracuda_z3n Package

continuing_barracuda_z3n Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-93775: Malicious code in continuing_barracuda_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 Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The continuing_barracuda_z3n package is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to facilitate the distribution of token rewards through various scripts. However, it has been identified as a malicious package that modifies its own metadata and publishes derivative versions to manipulate the npm registry.

Vulnerability Detail

The vulnerability originates from the malicious intent behind the continuing_barracuda_z3n package, which contains scripts that automatically generate and publish derivative packages with altered metadata. This includes removing private flags from package.json, changing version numbers, and creating random package names. The continuous republishing of these variants can lead to pollution of the npm registry, potentially affecting developers' reputations and the integrity of the ecosystem.

How To Fix

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

npm uninstall continuing_barracuda_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 continuing_barracuda_z3n package and consider alternative packages that provide similar functionality without the associated risks. Additionally, you can monitor your dependencies using tools like Vulert to identify any vulnerabilities in your project.

Conclusion

The continuing_barracuda_z3n package poses a significant risk due to its malicious code that modifies package metadata and floods the npm registry. It is crucial to remove this package from your project and monitor for vulnerabilities using tools like Vulert to maintain the integrity of your software.

See every vulnerability recorded for continuing_barracuda_z3n →

Share this vulnerability

FAQ

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

The vulnerability can lead to the pollution of the npm registry and may affect your project's integrity and reputation.

You should remove the continuing_barracuda_z3n package from your project immediately.

Yes, you can use Vulert to monitor and alert for open-source vulnerabilities in your software without requiring code access.

You can use the Vulert playground at Vulert Scanner to check if your application is affected without any signup.

How To Fix

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

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