Malicious Code Injection in Costly Dove Z3N Package

costly_dove_z3n Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-101030: Malicious code in costly_dove_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 Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

Costly Dove Z3N is an npm package that is part of the tea.xyz token reward campaign. It is designed to facilitate token rewards through various functionalities. However, it has been identified as a malicious package that employs scripts to manipulate its own metadata and publish numerous derivative packages, leading to potential security risks for developers and users.

Vulnerability Detail

The vulnerability originates from the package's malicious payload, which modifies the package.json file to remove private flags and alters version numbers. It generates random package names and continuously republishes these variants to the npm registry, thereby polluting it. This behavior can lead to reputation inflation for developers and may expose users to untrusted code, increasing the risk of security breaches.

How To Fix

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

npm uninstall costly_dove_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 prevent the installation of this malicious package by using npm's package-lock.json to monitor dependencies. Ensure that your project does not include costly_dove_z3n by checking your package.json and removing any references to it.

Conclusion

The costly_dove_z3n package has been identified as a malicious entity within the npm ecosystem, posing significant risks to developers and users alike. It is crucial to remove this package and monitor your dependencies to maintain the integrity of your applications.

See every vulnerability recorded for costly_dove_z3n →

Share this vulnerability

FAQ

The malicious code modifies package metadata and publishes numerous derivative packages to inflate developer reputation scores.

You can use Vulert, which monitors open-source vulnerabilities in real-time. Visit Vulert Scanner to check your application without any signup.

Using this package can expose your application to untrusted code, leading to potential security breaches and reputation damage.

Yes, you can monitor your dependencies using package-lock.json and ensure that costly_dove_z3n is not included in your project.

You should uninstall the package immediately using 'npm uninstall costly_dove_z3n' and check for any other affected packages.

How To Fix

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

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