Malicious Code Injection in secure_barracuda_z3n Package

secure_barracuda_z3n Updated 18 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-108493: Malicious code in secure_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 Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

The secure_barracuda_z3n package is part of the npm ecosystem, often utilized in various JavaScript applications. It is designed to facilitate certain functionalities within projects but has been compromised by malicious actors. This package is linked to a broader campaign that aims to manipulate the npm registry by flooding it with derivative packages, thereby inflating developer reputation scores for token rewards.

Vulnerability Detail

The vulnerability in the secure_barracuda_z3n package originates from its association with the tea.xyz token reward campaign. It includes malicious scripts that modify the package.json file by removing private flags, altering version numbers, and generating random package names. This behavior leads to the continuous republishing of variants, which pollutes the npm registry and poses a risk to developers relying on this package, potentially leading to reputation damage and security breaches.

How To Fix

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

npm uninstall secure_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 secure_barracuda_z3n package from your project by executing the following command: npm uninstall secure_barracuda_z3n. This will prevent the malicious code from executing until a secure version is available.

Conclusion

The secure_barracuda_z3n package has been identified as containing malicious code that can compromise the integrity of projects using it. It is essential to take immediate action by updating or removing the package to safeguard your application from potential threats.

See every vulnerability recorded for secure_barracuda_z3n →

Share this vulnerability

FAQ

The secure_barracuda_z3n package is an npm package used in JavaScript applications, but it has been compromised with malicious code.

The malicious code modifies your package.json file and can lead to the continuous republishing of variants, which may damage your project's reputation and security.

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

If you cannot update the package, consider uninstalling it temporarily to prevent any malicious activity until a secure version is available.

Detailed information about this vulnerability can be found in the official npm registry and security advisories related to the secure_barracuda_z3n package.

How To Fix

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

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