Malicious Code Detected in dmstools Package - Security Alert

dmstools Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-18541: Malicious code in dmstools (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 dmstools package is an npm library designed for data management and manipulation tasks. It provides various utilities for developers to streamline their workflow. However, recent findings have revealed that this package contains malicious code, posing a significant risk to users who incorporate it into their projects.

Vulnerability Detail

The vulnerability stems from the presence of malicious code within the dmstools package, which was introduced in version 0 and affects all subsequent versions. This malicious code can lead to unauthorized access, data breaches, or other harmful actions that compromise the integrity of applications using this package. Users are at risk of having their systems exploited if they do not take immediate action.

How To Fix

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

npm uninstall dmstools

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, users can avoid using the dmstools package altogether and look for alternative libraries that provide similar functionality without the associated risks. Additionally, consider using tools like Vulert to monitor your project for vulnerabilities.

Conclusion

The discovery of malicious code in the dmstools package poses a serious threat to users. It is crucial to take immediate action by removing the package and monitoring for any updates or alternatives. Utilizing tools like Vulert can help ensure ongoing security in your projects.

See every vulnerability recorded for dmstools →

Share this vulnerability

FAQ

dmstools is an npm package designed for data management and manipulation tasks, providing various utilities for developers.

The malicious code can lead to unauthorized access and potential data breaches, compromising the security of applications using the package.

You can use the Vulert platform to monitor and alert for open-source vulnerabilities in your software. Check your application using the Vulert playground at Vulert Scanner.

Currently, there is no patched version available. Users are advised to remove the package and look for alternatives.

Remove the dmstools package from your project immediately and replace it with a secure alternative to mitigate any risks.

How To Fix

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

npm uninstall dmstools

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