Malicious Code Detected in acceptable_tuna_z3n Package: A Threat to npm Users

acceptable_tuna_z3n Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-93093: Malicious code in acceptable_tuna_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 acceptable_tuna_z3n package is part of the npm ecosystem and has been identified as a malicious package linked to the tea.xyz token reward campaign. This package is designed to manipulate npm's registry by generating and publishing numerous derivative packages with randomized names, aiming to inflate developer reputation scores for token rewards. Its functionality is primarily centered around automating the publication of these packages, which can lead to significant pollution of the npm registry.

Vulnerability Detail

The vulnerability stems from the presence of malicious code within the acceptable_tuna_z3n package. This code modifies the package.json file by removing private flags, altering version numbers, and generating random package names. The malicious payload continuously republishes these variants, which can lead to the npm registry being flooded with unwanted packages, potentially affecting the integrity and reliability of the ecosystem. This poses a risk to developers who may unknowingly install these compromised packages, leading to security breaches or other unintended consequences.

How To Fix

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

npm uninstall acceptable_tuna_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 acceptable_tuna_z3n package altogether and look for alternative packages that provide similar functionality without the associated risks. Always verify the source and reputation of packages before installation.

Conclusion

The acceptable_tuna_z3n package poses a significant threat to npm users due to its malicious code designed to manipulate the npm registry. It is essential to remove this package from your projects and stay vigilant about the packages you use. Utilizing tools like Vulert can help you monitor for vulnerabilities effectively.

See every vulnerability recorded for acceptable_tuna_z3n →

Share this vulnerability

FAQ

The acceptable_tuna_z3n package is a malicious npm package linked to a token reward campaign that automates the publication of derivative packages.

If you have the acceptable_tuna_z3n package installed, your project may be at risk of being polluted with unwanted packages, which can lead to security vulnerabilities.

You should uninstall the acceptable_tuna_z3n package immediately and review your project's dependencies for any other potentially malicious packages.

You can use tools like Vulert, which monitors your package-lock.json file to alert you in real-time for open-source vulnerabilities. You can check your application using the Vulert playground without any signup.

Yes, consider looking for other npm packages that offer similar functionality but have a good reputation and are not associated with malicious activities.

How To Fix

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

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