Malicious Code Detected in dohamark Package - Security Alert

dohamark Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-18599: Malicious code in dohamark (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 dohamark package is an npm library designed for various functionalities within JavaScript applications. It is commonly used for its ease of integration and utility in handling specific tasks. However, recent findings have revealed that this package contains malicious code, posing significant security risks to applications that utilize it.

Vulnerability Detail

The vulnerability stems from the presence of malicious code within the dohamark package, which was introduced in version 0. This malicious code can potentially compromise the integrity of applications that depend on this package, leading to unauthorized access, data breaches, or other harmful effects. The origin of this issue is linked to the package's codebase, which has been tampered with to include harmful scripts.

How To Fix

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

npm uninstall dohamark

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

Conclusion

The discovery of malicious code in the dohamark package highlights the importance of regularly monitoring and updating dependencies in software projects. By following the recommended steps to fix the vulnerability and utilizing tools like Vulert, developers can enhance the security of their applications.

See every vulnerability recorded for dohamark →

Share this vulnerability

FAQ

dohamark is an npm package used in JavaScript applications for various functionalities, but it has been found to contain malicious code.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check if your application is affected without needing to sign up.

Using the dohamark package can lead to unauthorized access, data breaches, and other security issues due to the embedded malicious code.

Yes, you can temporarily uninstall the dohamark package and look for alternative packages that offer similar functionalities without the security risks.

Utilize tools like Vulert, which can monitor your package-lock.json file and alert you to any vulnerabilities in real-time.

How To Fix

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

npm uninstall dohamark

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