Malicious Code Injection in Costly Barracuda Z3N Package

costly_barracuda_z3n Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-101028: Malicious code in costly_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 'costly_barracuda_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 publication of derivative packages, which can inflate developer reputation scores for token rewards. However, it has been compromised to include malicious scripts that alter package metadata.

Vulnerability Detail

The vulnerability originates from the inclusion of malicious code within the 'costly_barracuda_z3n' package. This 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. The ramifications include potential security risks for developers who unknowingly use this package, as it can lead to unauthorized access or manipulation of their projects.

How To Fix

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

npm uninstall costly_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 remove the 'costly_barracuda_z3n' package from your project by executing: npm uninstall costly_barracuda_z3n. This will prevent any malicious code from executing until a secure version is available.

Conclusion

The 'costly_barracuda_z3n' package has been identified as containing malicious code that can compromise the integrity of projects using it. It is crucial to update or remove this package to safeguard your application from potential threats.

See every vulnerability recorded for costly_barracuda_z3n →

Share this vulnerability

FAQ

It is an npm package associated with the tea.xyz token reward campaign, designed to generate and publish derivative packages.

The malicious code modifies your package.json file, which can lead to unauthorized changes in your project and potential security vulnerabilities.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check your application without needing to sign up.

As a workaround, you can uninstall the 'costly_barracuda_z3n' package to prevent any malicious code from executing.

Detailed information about this vulnerability can be found in the official npm registry or security advisories related to the 'costly_barracuda_z3n' package.

How To Fix

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

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