Malicious Code Injection in compact_barracuda_z3n: A Threat to npm Packages

compact_barracuda_z3n Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-93656: Malicious code in compact_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 package compact_barracuda_z3n is part of the npm ecosystem, which is widely used for JavaScript package management. This package, like many others, is designed to facilitate the development and distribution of JavaScript applications. However, it has been identified as part of a malicious campaign that aims to exploit the npm registry by generating and publishing derivative packages with harmful scripts.

Vulnerability Detail

The vulnerability in compact_barracuda_z3n stems from its association with a malicious campaign that floods the npm registry with fake packages. These packages contain scripts that modify the package.json file to remove private flags, alter version numbers, and generate random package names. This not only compromises the integrity of the npm registry but also poses a risk to developers who may unknowingly install these malicious packages, leading to potential security breaches in their applications.

How To Fix

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

npm uninstall compact_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 measure, avoid using the compact_barracuda_z3n package and consider using alternative packages that provide similar functionality without the associated risks.

Conclusion

The compact_barracuda_z3n package poses a significant risk due to its association with a malicious npm campaign. It is essential for developers to be vigilant about the packages they use and to take immediate action if they are affected by this vulnerability. Regular monitoring and updates can help safeguard applications from such threats.

See every vulnerability recorded for compact_barracuda_z3n →

Share this vulnerability

FAQ

compact_barracuda_z3n is an npm package that has been identified as part of a malicious campaign to flood the npm registry with harmful scripts.

You can use Vulert, which monitors open-source vulnerabilities in real-time. By uploading your package-lock.json file, you can check for vulnerabilities without any installation required.

If you have installed compact_barracuda_z3n, you should uninstall it immediately using 'npm uninstall compact_barracuda_z3n' and review your dependencies for any other potentially harmful packages.

Yes, the malicious payload modifies package.json files and republishes variants to pollute the npm registry, which can lead to security breaches in applications that use these packages.

To prevent similar vulnerabilities, always use trusted packages, regularly update your dependencies, and utilize tools like Vulert to monitor for vulnerabilities in your projects.

How To Fix

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

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