Critical Malicious Code Vulnerability in responses-starter-app Package

responses-starter-app Updated 13 Feb 2026

Summary

13/02/2026
CRITICAL
No i
Critical
Not published

MAL-2026-889: Malicious code in responses-starter-app (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 MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

The responses-starter-app is an npm package designed to facilitate the creation of response-based applications. It offers developers a streamlined way to manage responses in their applications. However, this package has been identified as containing malicious code, posing significant security risks to any system utilizing it.

Vulnerability Detail

The vulnerability stems from the presence of embedded malicious code within the responses-starter-app package. This code can compromise any computer that has the package installed or running, allowing unauthorized access to sensitive information such as secrets and keys. The malicious nature of this code means that simply removing the package may not eliminate all traces of the compromise, as full control of the computer may have been granted to an external entity.

How To Fix

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

npm uninstall responses-starter-app

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, if you must continue development while addressing this vulnerability, consider using an alternative package that provides similar functionality without the associated risks. Always ensure to monitor your dependencies for vulnerabilities using tools like Vulert, which can alert you in real-time for open-source vulnerabilities.

Conclusion

The responses-starter-app package has been identified as containing malicious code that poses a serious security risk. Immediate action is required to remove the package and secure any sensitive information. Utilizing tools like Vulert can help in monitoring for such vulnerabilities in the future.

See every vulnerability recorded for responses-starter-app →

Share this vulnerability

FAQ

Immediately remove the package and rotate any sensitive information stored on the affected system.

You can use the Vulert playground at Vulert Scanner to check if your application is affected without requiring any signup.

While removing the package is necessary, be aware that it may not eliminate all malicious software that has been installed as a result of the compromise.

Failing to address this vulnerability can lead to unauthorized access to sensitive data, potential data breaches, and complete system compromise.

Yes, tools like Vulert can monitor your package dependencies and alert you to any open-source vulnerabilities in real-time.

How To Fix

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

npm uninstall responses-starter-app

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