Malicious Code Detected in dztools Package - Security Alert

dztools Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-19049: Malicious code in dztools (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 Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The dztools package is an npm library designed to provide various utility functions for developers. It is widely used in JavaScript projects for its ease of integration and functionality. However, recent findings have revealed that this package contains malicious code, posing a significant risk to users who have integrated it into their applications.

Vulnerability Detail

The dztools package has been identified to contain malicious code that can compromise the security of applications utilizing it. This vulnerability originated from the package's source code, which was found to be intentionally crafted to execute harmful operations. Users of dztools are at risk of data breaches, unauthorized access, and other security threats due to this malicious code.

How To Fix

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

npm uninstall dztools

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 replace dztools with alternative packages that provide similar functionality without the associated risks. Review your project's dependencies and consider using well-maintained and trusted libraries.

Conclusion

The discovery of malicious code in the dztools package highlights the importance of regularly auditing dependencies in software projects. Users are strongly advised to remove this package and consider alternatives to safeguard their applications from potential security threats.

See every vulnerability recorded for dztools →

Share this vulnerability

FAQ

dztools is an npm package that offers utility functions for JavaScript developers, but it has been found to contain malicious code.

You can check if your application is affected by using Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to analyze your package-lock.json without any signup.

If you have dztools installed, you should uninstall it immediately using 'npm uninstall dztools' and look for alternative packages.

Continuing to use dztools poses a risk to your data and application security due to the malicious code present in the package.

Currently, there is no patch available for dztools. The recommended action is to uninstall the package and seek alternatives.

How To Fix

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

npm uninstall dztools

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