Malicious Code Injection in digital_dove_z3n Package - npm Vulnerability

digital_dove_z3n Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-101570: Malicious code in digital_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 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 digital_dove_z3n package is part of the npm ecosystem, which is widely used for JavaScript package management. This package has been identified as part of a malicious campaign that aims to exploit npm's publishing mechanisms. It is designed to generate and publish derivative packages with randomized names, which can inflate developer reputation scores for token rewards in the tea.xyz protocol. The presence of malicious scripts within this package poses a significant risk to developers and users relying on npm for secure package management.

Vulnerability Detail

The vulnerability in the digital_dove_z3n package stems from its inclusion in a malicious campaign that modifies the package.json file to remove private flags and change version numbers. It generates random package names and continuously republishes variants, polluting the npm registry. This behavior can lead to the proliferation of untrustworthy packages, potentially compromising the security of applications that depend on them. The malicious payload is designed to exploit npm's publishing system, making it difficult for developers to identify and mitigate the risks associated with these packages.

How To Fix

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

npm uninstall digital_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 workaround, avoid using the digital_dove_z3n package and consider using alternative packages that provide similar functionality without the associated risks. Regularly audit your package dependencies to ensure they are secure.

Conclusion

The digital_dove_z3n package has been identified as a malicious package that poses significant risks to developers and applications using npm. It is crucial to remove this package and monitor your dependencies for vulnerabilities. Utilizing tools like Vulert can help maintain the security of your applications by providing real-time alerts for open-source vulnerabilities.

See every vulnerability recorded for digital_dove_z3n →

Share this vulnerability

FAQ

The digital_dove_z3n package is an npm package that has been identified as part of a malicious campaign aimed at exploiting npm's publishing mechanisms.

The vulnerability can lead to the inclusion of untrustworthy packages in your application, potentially compromising its security and integrity.

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

You can use Vulert to monitor your application for open-source vulnerabilities in real-time. Vulert utilizes package-lock.json to alert you of any vulnerabilities without requiring code access or installation.

Yes, 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 digital_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