Malicious Code in simple-autocomplete-dropdown (npm)

simple-autocomplete-dropdown Updated 02 Oct 2025

Summary

28/11/2023
CRITICAL
No i
Critical
Not published

MAL-2023-8623: Malicious code in simple-autocomplete-dropdown (npm). Affects simple-autocomplete-dropdown versions 3.7.14. 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 simple-autocomplete-dropdown package is an npm package that provides functionality for creating autocomplete dropdowns in web applications. It allows users to easily search and select options from a dropdown list. The package is widely used in various web development projects.

Vulnerability Detail

The simple-autocomplete-dropdown package version 3.7.14 has been identified as malicious by the OpenSSF Package Analysis project. The package communicates with a domain associated with malicious activity. This poses a significant security risk as it can potentially compromise the integrity and security of the affected web applications. Attackers may exploit this vulnerability to execute arbitrary code, steal sensitive information, or perform other malicious actions.

How To Fix

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

npm uninstall simple-autocomplete-dropdown

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

There is no known workaround for this vulnerability. It is necessary to remove the affected package and follow the recommended steps for remediation.

Conclusion

The simple-autocomplete-dropdown package version 3.7.14 has been identified as malicious and poses a significant security risk. It is recommended to immediately remove the affected package from your project and replace it with a non-malicious version or an alternative package. Regularly updating and monitoring the packages used in your project is essential to ensure the security and integrity of your web applications. For further support and assistance in vulnerability remediation, you can contact DevNack.com.

See every vulnerability recorded for simple-autocomplete-dropdown →

Share this vulnerability

FAQ

You can use the Vulert Playground at Vulert Scanner to check if your application is affected by this specific vulnerability. Simply upload your package-lock.json file and Vulert will analyze it in real-time to identify any open-source vulnerabilities.

Yes, there are several alternative autocomplete dropdown packages available in the npm ecosystem. Some popular options include 'react-autocomplete', 'downshift', and 'react-select'. It is recommended to choose a package with a good track record of security and regular updates.

Manually removing the malicious code from the affected package is not recommended. The codebase may be complex, and there is a risk of missing or introducing errors during the removal process. It is best to completely remove the affected package and replace it with a non-malicious version or an alternative package.

The potential consequences of this vulnerability include unauthorized code execution, data breaches, and compromise of sensitive information. Attackers may exploit this vulnerability to inject malicious code, steal user credentials, or gain unauthorized access to the affected system.

To prevent similar vulnerabilities in the future, it is crucial to regularly update and monitor the packages used in your project. Stay informed about security advisories and vulnerabilities related to the packages you depend on. Consider using automated vulnerability scanning tools like Vulert to proactively identify and address potential security risks.

How To Fix

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

npm uninstall simple-autocomplete-dropdown

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