Malicious Code Detected in Dragonbar Package - Vulnerability MAL-2025-18757

dragonbar Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-18757: Malicious code in dragonbar (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 Dragonbar package is an npm library designed for creating interactive user interfaces. It offers various functionalities that enhance user experience in web applications. However, it has been identified to contain malicious code, posing significant security risks to applications that utilize this package.

Vulnerability Detail

The vulnerability in the Dragonbar package originates 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 vulnerability is classified under the identifier MAL-2025-18757 and affects all versions starting from 0.

How To Fix

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

npm uninstall dragonbar

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

If an immediate update is not feasible, consider removing the Dragonbar package from your project temporarily until a secure version is available. You can uninstall it using the command: npm uninstall dragonbar.

Conclusion

The Dragonbar package has been identified to contain malicious code, posing a significant risk to applications that utilize it. It is crucial to update to a patched version or remove the package until a secure version is available. Utilizing tools like Vulert can help monitor and manage vulnerabilities effectively.

See every vulnerability recorded for dragonbar →

Share this vulnerability

FAQ

Dragonbar is an npm package used for creating interactive user interfaces in web applications.

This vulnerability indicates the presence of malicious code within the Dragonbar package, which can compromise application security.

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

As a temporary measure, you can uninstall the Dragonbar package from your project to mitigate the risk until a secure version is available.

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

How To Fix

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

npm uninstall dragonbar

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