Malicious Code Injection in main_barnacle_z3n Package - npm Vulnerability

main_barnacle_z3n Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-95354: Malicious code in main_barnacle_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 main_barnacle_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 automatic generation and publication of derivative packages, which can inflate developer reputation scores. However, it has been identified as containing malicious code that compromises the integrity of the npm registry.

Vulnerability Detail

The vulnerability originates from the package's malicious payload, which modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior leads to the continuous republishing of variants, polluting the npm registry and potentially harming developers' reputations and the integrity of the ecosystem. The malicious scripts are designed to exploit the npm infrastructure for nefarious purposes.

How To Fix

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

npm uninstall main_barnacle_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, you can avoid using the main_barnacle_z3n package and any other packages associated with the tea.xyz token reward campaign. Regularly audit your dependencies to ensure that no malicious packages are included.

Conclusion

The main_barnacle_z3n package contains malicious code that compromises the npm registry and can affect developers' reputations. It is crucial to remove this package from your project and monitor your dependencies for any malicious activity. Utilizing tools like Vulert can help you stay informed about vulnerabilities in your open-source software.

See every vulnerability recorded for main_barnacle_z3n →

Share this vulnerability

FAQ

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

The malicious code modifies your package.json, removes private flags, and can lead to the pollution of the npm registry, affecting your project's integrity.

You should uninstall the main_barnacle_z3n package immediately using the command npm uninstall main_barnacle_z3n.

Yes, you can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. You can check your application using the Vulert playground at Vulert Scanner.

Currently, there is no patched version available. The best course of action is to remove the affected package from your project.

How To Fix

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

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