Malicious Code Detected in dmodcode Package - MAL-2025-18539

dmodcode Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-18539: Malicious code in dmodcode (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 MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

The dmodcode package is an npm library designed for developers to facilitate various coding tasks. It is widely used in JavaScript projects for its utility functions. However, it has recently been identified as containing malicious code, which poses significant security risks to applications that utilize this package.

Vulnerability Detail

The vulnerability in the dmodcode package stems from the inclusion of malicious code that can compromise the security of applications using it. This code may lead to unauthorized access, data breaches, or other harmful actions within the affected systems. The issue was introduced in version 0 and affects all subsequent versions, making it critical for users to address this vulnerability promptly.

How To Fix

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

npm uninstall dmodcode

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 remove the dmodcode package from your project until a secure version is released. Use the following command to uninstall the package: 'npm uninstall dmodcode'. This will prevent any malicious code from executing in your application.

Conclusion

The dmodcode package has been found to contain malicious code, posing significant security risks to applications. It is crucial for developers to update or remove the package to protect their projects from potential threats. Utilizing tools like Vulert can help monitor and manage vulnerabilities effectively.

See every vulnerability recorded for dmodcode →

Share this vulnerability

FAQ

dmodcode is an npm package used for various coding tasks in JavaScript projects.

The malicious code was identified by security researchers from Amazon Inspector, who reported it as a vulnerability.

Using the compromised package can lead to unauthorized access, data breaches, and potential damage to your application.

Users should check the npm repository for any patched versions of the dmodcode package to ensure they are using a secure version.

You can use Vulert, which monitors and alerts in real-time for open-source vulnerabilities using just the package-lock.json file. You can also check if your application is affected by this vulnerability using the Vulert playground at Vulert Scanner without any signup.

How To Fix

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

npm uninstall dmodcode

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