Critical Malicious Code Vulnerability in create-react-app-lambda Package

create-react-app-lambda Updated 08 Jan 2026

Summary

07/01/2026
CRITICAL
No i
Critical
Not published

MAL-2026-132: Malicious code in create-react-app-lambda (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 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

create-react-app-lambda is an npm package designed to facilitate the deployment of React applications on AWS Lambda. It streamlines the process of creating serverless applications by providing a set of tools and configurations. However, this package has been compromised, leading to severe security risks for users who have it installed.

Vulnerability Detail

The vulnerability stems from malicious code embedded within the create-react-app-lambda package. This code can fully compromise any computer that has the package installed, allowing unauthorized access to sensitive data, including secrets and keys. The origin of this issue is linked to a malicious actor who injected harmful code into the package, making it a significant threat to users and their systems.

How To Fix

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

npm uninstall create-react-app-lambda

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

Currently, the only effective workaround is to uninstall the create-react-app-lambda package. You can do this by executing the following command in your terminal: npm uninstall create-react-app-lambda. However, be aware that simply removing the package may not eliminate all traces of the malicious software.

Conclusion

The create-react-app-lambda package has been compromised with malicious code, posing a significant risk to users. Immediate action is required to uninstall the package and secure any sensitive information. Monitoring tools like Vulert can assist in identifying vulnerabilities in your applications.

See every vulnerability recorded for create-react-app-lambda →

Share this vulnerability

FAQ

Immediately uninstall the package and rotate any sensitive information stored on your system.

You can use Vulert's playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.

As of now, there is no patched version available. The best course of action is to uninstall the package.

Failing to address this vulnerability can lead to unauthorized access to your system, data breaches, and potential loss of sensitive information.

It is advisable to avoid using create-react-app-lambda until the maintainers have addressed the security issues and released a verified safe version.

How To Fix

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

npm uninstall create-react-app-lambda

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