Malicious Code Detected in dandelion-dune-cli341-project: A Critical Security Alert

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-17946: Malicious code in dandelion-dune-cli341-project (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 dandelion-dune-cli341-project is an npm package designed for various command-line interface functionalities. It is utilized by developers for its ease of integration and utility in managing tasks within Node.js environments. However, recent findings have revealed that this package contains malicious code, posing significant security risks to users and their applications.

Vulnerability Detail

The vulnerability in the dandelion-dune-cli341-project stems from the inclusion of malicious code that can compromise the integrity of applications using this package. This code may lead to unauthorized access, data breaches, or other harmful actions that can affect both the application and its users. The malicious code was introduced in version 0 and has not been rectified in subsequent releases, making it imperative for users to take immediate action.

How To Fix

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

npm uninstall dandelion-dune-cli341-project

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 dandelion-dune-cli341-project package from your project by executing the following command: npm uninstall dandelion-dune-cli341-project. This will prevent the execution of any malicious code while you await a secure update.

Conclusion

The discovery of malicious code in the dandelion-dune-cli341-project package highlights the importance of vigilance in managing open-source dependencies. Users are urged to take immediate action to protect their applications by updating or removing the affected package. Utilizing tools like Vulert can further enhance security by providing real-time vulnerability alerts.

See every vulnerability recorded for dandelion-dune-cli341-project →

Share this vulnerability

FAQ

The malicious code is designed to exploit vulnerabilities in applications, potentially leading to unauthorized access and data breaches.

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

Currently, there is no patched version available for the dandelion-dune-cli341-project package. Users are advised to uninstall the package until a secure version is released.

If immediate removal is not possible, ensure that your application has additional security measures in place to mitigate potential risks until you can update or remove the package.

Vulert uses the package-lock.json file to monitor and alert users in real-time about 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 dandelion-dune-cli341-project

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