Malicious Code in dropdown-input (npm)

dropdown-input Updated 02 Oct 2025

Summary

28/11/2023
CRITICAL
No i
Critical
Not published

MAL-2023-8622: Malicious code in dropdown-input (npm). Affects dropdown-input versions 3.4.15. 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 dropdown-input package is an npm package that provides functionality for creating dropdown input fields in web applications. It allows developers to easily implement dropdown menus with customizable options. However, version 3.4.15 of the package has been identified as malicious by the OpenSSF Package Analysis project. This package communicates with a domain associated with malicious activity, making it a potential security risk for applications that use it.

Vulnerability Detail

The vulnerability in dropdown-input version 3.4.15 lies in its communication with a domain linked to malicious activity. This behavior indicates that the package may be compromised or used for malicious purposes. The exact nature and impact of the malicious activity are not specified in the provided information, but it poses a potential threat to the security and integrity of applications that include this package. It is crucial to address this vulnerability promptly to prevent any potential harm to the application or its users.

How To Fix

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

npm uninstall dropdown-input

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 workaround, you can manually modify the package code to remove the communication with the malicious domain. However, this approach is not recommended as it may introduce further issues and is not a sustainable solution. It is best to follow the recommended fix and update the package to a safe version.

Conclusion

The dropdown-input package version 3.4.15 has been identified as malicious due to its communication with a domain associated with malicious activity. To ensure the security and integrity of your application, it is crucial to remove this version from your dependencies and update to a safe version. Following the recommended fix and regularly monitoring your application for vulnerabilities using tools like Vulert can help safeguard your software against potential threats. For further support on vulnerability remediation, you can contact DevNack.com.

See every vulnerability recorded for dropdown-input →

Share this vulnerability

FAQ

Dropdown-input is an npm package that provides functionality for creating dropdown input fields in web applications. It simplifies the process of implementing dropdown menus with customizable options.

The vulnerability in dropdown-input version 3.4.15 involves communication with a domain associated with malicious activity. This can potentially compromise the security and integrity of your application, allowing unauthorized access or other malicious actions.

Yes, the recommended fix is to remove the affected version of dropdown-input (3.4.15) from your application's dependencies and update to a safe version of the package.

While a workaround is possible by manually modifying the package code to remove the communication with the malicious domain, it is not recommended. Workarounds may introduce further issues and are not sustainable solutions. It is best to follow the recommended fix and update the package.

You can use tools like Vulert (https://vulert.com) to monitor and alert in real-time for open-source vulnerabilities in your software. Vulert uses package-lock.json to identify and notify you about any vulnerabilities, including the one in dropdown-input.

How To Fix

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

npm uninstall dropdown-input

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