Malicious Code Vulnerability in mechanical_marlin_z3n Package

mechanical_marlin_z3n Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-98810: Malicious code in mechanical_marlin_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 Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

Background

The mechanical_marlin_z3n package is part of the npm ecosystem, designed to facilitate various functionalities within JavaScript applications. However, it has been identified as part of a malicious campaign that floods the npm registry with derivative packages. This package is particularly vulnerable due to its association with scripts that manipulate package metadata for nefarious purposes.

Vulnerability Detail

The vulnerability originates from the mechanical_marlin_z3n package being part of a larger malicious scheme associated with the tea.xyz token reward campaign. It contains scripts that automatically modify the package.json file to remove private flags, alter version numbers, and generate random package names. This leads to the continuous republishing of variants, which can pollute the npm registry and inflate developer reputation scores fraudulently. The ramifications include potential security risks for applications using this package, as well as the degradation of the npm ecosystem.

How To Fix

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

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

Conclusion

The mechanical_marlin_z3n package has been identified as containing malicious code that can compromise the integrity of applications using it. It is crucial to update or remove this package to protect your application from potential security threats. Utilizing tools like Vulert can help monitor and manage vulnerabilities effectively.

See every vulnerability recorded for mechanical_marlin_z3n →

Share this vulnerability

FAQ

The mechanical_marlin_z3n package is an npm package that has been identified as part of a malicious campaign, designed to manipulate package metadata and inflate developer reputation scores.

This vulnerability can lead to security risks, including the potential for malicious code execution and the pollution of the npm registry, which may affect the integrity of your application's dependencies.

You can use Vulert to monitor and alert for open-source vulnerabilities in your software. By utilizing the Vulert playground, you can check if your application is affected by this vulnerability without any signup.

If you cannot update the package, consider removing it from your project as a temporary measure to mitigate risks associated with the vulnerability.

More information can be found in the vulnerability report on the official GitHub repository or by consulting security advisories related to npm packages.

Sponsored Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

How To Fix

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

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