Malicious Code Injection in delicate_marlin_z3n Package - npm Vulnerability

delicate_marlin_z3n Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-101303: Malicious code in delicate_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 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 delicate_marlin_z3n package is part of the npm ecosystem, which is widely used for managing JavaScript packages. This package has been identified as part of a malicious campaign that aims to exploit the npm registry by flooding it with derivative packages. These packages are designed to inflate developer reputation scores through automated publishing scripts, which can lead to significant issues within the ecosystem.

Vulnerability Detail

The vulnerability in the delicate_marlin_z3n package originates from its association with the tea.xyz token reward campaign. It contains malicious scripts that modify the package.json file to remove private flags, alter version numbers, and generate random package names. This behavior leads to the continuous republishing of variants, polluting the npm registry and potentially compromising other packages and applications that depend on it.

How To Fix

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

npm uninstall delicate_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 measure, you can avoid using the delicate_marlin_z3n package and any other packages that may be associated with the tea.xyz campaign. Regularly audit your package dependencies using tools like npm audit to identify and address vulnerabilities.

Conclusion

The delicate_marlin_z3n package poses a significant risk due to its malicious code designed to manipulate the npm registry. It is crucial for developers to be vigilant and remove this package from their projects to maintain the integrity of their applications. Regular audits and monitoring using tools like Vulert can help in identifying and mitigating such vulnerabilities.

See every vulnerability recorded for delicate_marlin_z3n →

Share this vulnerability

FAQ

The delicate_marlin_z3n package is an npm package that has been identified as part of a malicious campaign aimed at inflating developer reputation scores through automated publishing.

This vulnerability can lead to the pollution of the npm registry, potentially compromising other packages and applications that rely on npm for dependency management.

If you have installed the delicate_marlin_z3n package, you should uninstall it immediately using the command npm uninstall delicate_marlin_z3n.

You can use tools like Vulert, which monitors and alerts in real-time for open-source vulnerabilities using just your package-lock.json file. You can also check your application against known vulnerabilities using the Vulert playground.

There is no patch for the delicate_marlin_z3n package itself, as it is recommended to remove it entirely from your project.

How To Fix

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

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