Malicious Code Injection in mammoth_fish_z3n Package

mammoth_fish_z3n Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-95370: Malicious code in mammoth_fish_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 MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

The mammoth_fish_z3n package is part of the npm ecosystem, often utilized in JavaScript projects for various functionalities. However, it has been identified as part of a malicious campaign that floods the npm registry with derivative packages. This package is designed to manipulate developer reputation scores through automated publishing scripts, which can lead to significant security risks for users relying on it.

Vulnerability Detail

The vulnerability stems from the malicious code embedded within the mammoth_fish_z3n package. This code modifies the package.json file by removing private flags, altering version numbers, and generating random package names. The intent is to continuously republish these variants, polluting the npm registry and potentially compromising the integrity of projects that depend on this package. The origin of this vulnerability is linked to the tea.xyz token reward campaign, which exploits npm's publishing mechanisms.

How To Fix

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

npm uninstall mammoth_fish_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 mammoth_fish_z3n package and look for alternative packages that provide similar functionality without the associated risks. Additionally, you can monitor your project for any unauthorized changes to the package.json file.

Conclusion

The mammoth_fish_z3n package poses a significant security risk due to its malicious code that alters project files and publishes unauthorized variants. It is crucial for developers to remove this package and monitor their projects for any potential vulnerabilities. Utilizing tools like Vulert can aid in maintaining the security of your software.

See every vulnerability recorded for mammoth_fish_z3n →

Share this vulnerability

FAQ

The mammoth_fish_z3n package is an npm package that has been identified as part of a malicious campaign to manipulate developer reputation scores.

This vulnerability can lead to unauthorized modifications in your project, potentially compromising its integrity and security.

You should uninstall the mammoth_fish_z3n package immediately and check your project for any unauthorized changes.

Yes, you can use Vulert, which monitors and alerts for open-source vulnerabilities in your software using just package-lock.json.

You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.

How To Fix

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

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