Malicious Code Detected in dawgram: A Critical npm Vulnerability

dawgram Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-18073: Malicious code in dawgram (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 package dawgram is an npm library designed for specific functionalities within JavaScript applications. It is utilized for various tasks, but recent findings have revealed that it contains malicious code, posing significant risks to users and their applications. This vulnerability can lead to unauthorized access, data breaches, and other security issues.

Vulnerability Detail

The vulnerability in dawgram originates from the inclusion of malicious code within the package. This code can execute harmful actions without the user's consent, potentially compromising sensitive data and system integrity. The malicious nature of this code makes it imperative for users to take immediate action to safeguard their applications.

How To Fix

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

npm uninstall dawgram

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, users are advised to remove the dawgram package from their projects until a secure version is released. You can do this by executing the command: 'npm uninstall dawgram'. This will help prevent any potential exploitation of the malicious code.

Conclusion

The dawgram package has been identified as containing malicious code, posing significant risks to users. Immediate action is required to update or remove the package to protect applications from potential exploitation. Utilizing tools like Vulert can aid in monitoring for such vulnerabilities effectively.

See every vulnerability recorded for dawgram →

Share this vulnerability

FAQ

The malicious code can perform unauthorized actions, potentially leading to data breaches and system compromises.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check your application without any signup.

As a workaround, consider uninstalling the dawgram package until a secure version is available.

Currently, there is no patched version available. Users should monitor the package for updates and apply them as soon as they are released.

Vulert uses the package-lock.json file to monitor and alert users in real-time for open-source vulnerabilities, ensuring that your applications remain secure.

How To Fix

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

npm uninstall dawgram

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