Malicious Code Detected in dardasha Package - Security Alert

dardasha Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-17964: Malicious code in dardasha (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 Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

The dardasha package is an npm library designed for specific functionalities within JavaScript applications. It allows developers to integrate various features seamlessly. However, it has been identified to contain malicious code, posing a significant risk to applications that utilize it. This vulnerability can lead to unauthorized access or data manipulation, making it critical for developers to address it promptly.

Vulnerability Detail

The vulnerability in the dardasha package stems from the inclusion of malicious code that can compromise the security of applications using this package. This code can potentially allow attackers to execute harmful actions, such as data theft or unauthorized access to user information. The issue was introduced in version 0 and affects all subsequent versions. It is crucial for developers to be aware of this vulnerability to prevent exploitation.

How To Fix

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

npm uninstall dardasha

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 avoid using the dardasha package in your application until a secure version is released. Consider using alternative packages that provide similar functionality without the associated risks.

Conclusion

The discovery of malicious code in the dardasha package highlights the importance of maintaining secure coding practices and regularly monitoring dependencies. Developers are urged to take immediate action to remove the affected package and stay informed about updates to safeguard their applications.

See every vulnerability recorded for dardasha →

Share this vulnerability

FAQ

dardasha is an npm package designed for specific functionalities in JavaScript applications, but it has been found to contain malicious code.

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.

Remove the dardasha package from your project immediately and check for any updates or patches that may be released.

Regularly monitor your dependencies using tools like Vulert and keep your packages updated to the latest secure versions.

Using compromised packages can lead to data breaches, unauthorized access, and potential damage to your application's integrity and reputation.

How To Fix

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

npm uninstall dardasha

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