Critical Malicious Code Vulnerability in web-prompt Package

web-prompt Updated 03 Mar 2026

Summary

03/03/2026
CRITICAL
No i
Critical
Not published

MAL-2026-1184: Malicious code in web-prompt (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 web-prompt package is an npm library designed to facilitate interactive command-line prompts in Node.js applications. It allows developers to create user-friendly interfaces for input collection. However, this package has been identified as containing malicious code that compromises the security of any system it is installed on, making it a significant risk for developers and organizations using it.

Vulnerability Detail

The vulnerability originates from the inclusion of malicious code within the web-prompt package. This code can fully compromise any computer that has the package installed or running, allowing unauthorized access to sensitive information such as secrets and keys. The implications of this vulnerability are severe, as it may lead to data breaches and unauthorized control over affected systems. Users are advised to treat any system with this package as compromised.

How To Fix

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

npm uninstall web-prompt

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 are no effective workarounds for this vulnerability other than removing the package and securing the system. It is crucial to ensure that all sensitive information is rotated and that the system is monitored for any signs of compromise.

Conclusion

The web-prompt package has been identified as containing malicious code that poses a significant security risk. Users must take immediate action to remove the package and secure their systems. Utilizing tools like Vulert can help monitor for such vulnerabilities in the future.

See every vulnerability recorded for web-prompt →

Share this vulnerability

FAQ

Immediately remove the web-prompt package from your project and rotate any sensitive information stored on the affected system.

You can use Vulert, a tool that monitors and alerts for open-source vulnerabilities. Simply upload your package-lock.json file to the Vulert playground at Vulert Scanner to check for vulnerabilities.

Leaving the web-prompt package installed can lead to unauthorized access to your system, data breaches, and potential control by malicious actors.

Regularly monitor your dependencies using tools like Vulert, and keep your packages updated to the latest versions to mitigate security risks.

While many npm packages are safe, it is essential to review and monitor them regularly for vulnerabilities, as malicious packages can occasionally be published.

How To Fix

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

npm uninstall web-prompt

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