Critical Malicious Code Vulnerability in dmarnis Package

dmarnis Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-18532: Malicious code in dmarnis (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

The dmarnis package is an npm library designed for specific functionalities within JavaScript applications. It is utilized by developers for various tasks, but its integrity is compromised due to the presence of malicious code. This vulnerability poses significant risks to users who rely on this package for their projects.

Vulnerability Detail

The vulnerability in the dmarnis package stems from the inclusion of malicious code that can potentially harm users' systems. This code may lead to unauthorized access, data breaches, or other security issues. The vulnerability was introduced in version 0 and affects all subsequent versions, making it critical for users to address it immediately.

How To Fix

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

npm uninstall dmarnis

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 remove the dmarnis package from their project until a secure version is released. This can be done using the command: npm uninstall dmarnis. Consider using alternative packages that provide similar functionalities without the associated risks.

Conclusion

The dmarnis package contains a critical vulnerability due to malicious code that can compromise user systems. It is essential for developers to take immediate action by updating or removing the package until a secure version is released. Utilizing tools like Vulert can help in monitoring and managing open-source vulnerabilities effectively.

See every vulnerability recorded for dmarnis →

Share this vulnerability

FAQ

The malicious code can lead to unauthorized access and potential data breaches, posing a significant risk to users.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Check your application using the Vulert playground at Vulert Scanner.

As of now, there is no patched version available. Users should monitor the package repository for updates.

If immediate removal is not possible, consider isolating the package or limiting its use until a secure version is released.

Utilize tools like Vulert to monitor your dependencies for vulnerabilities and receive real-time alerts.

How To Fix

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

npm uninstall dmarnis

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