Critical Malicious Code Vulnerability in react-sdkk Package

react-sdkk Updated 04 Feb 2026

Summary

04/02/2026
CRITICAL
No i
Critical
Not published

MAL-2026-713: Malicious code in react-sdkk (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 Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The react-sdkk package is an npm library designed for integrating SDK functionalities into React applications. It provides developers with tools to streamline the implementation of various features. However, this package has been identified as containing malicious code, which poses significant security risks to any system utilizing it.

Vulnerability Detail

The vulnerability stems from the presence of embedded malicious code within the react-sdkk package. This code can compromise any computer that has the package installed, potentially allowing unauthorized access to sensitive information such as secrets and keys. The origin of this vulnerability is linked to malicious actors who have inserted harmful code into the package, making it a severe 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 react-sdkk

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 temporarily replace the functionalities provided by react-sdkk with alternative libraries that do not have known vulnerabilities. Ensure to review the security of any new packages before integrating them into your project.

Conclusion

The react-sdkk package has been identified as containing malicious code that poses a significant security threat. Users are advised to uninstall the package immediately and take necessary precautions to secure their sensitive information. Regular monitoring of dependencies using tools like Vulert can help prevent similar issues in the future.

See every vulnerability recorded for react-sdkk →

Share this vulnerability

FAQ

You should immediately uninstall the package and rotate any sensitive information that may have been compromised.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software. Visit Vulert Scanner to check your application without needing to sign up.

Currently, there is no patched version available for the react-sdkk package. The only course of action is to uninstall it.

Failing to address this vulnerability can lead to unauthorized access to sensitive data, potential data breaches, and full control of your system by malicious actors.

While many npm packages are safe, it is essential to conduct thorough security reviews and use tools like Vulert to monitor for vulnerabilities in any package you plan to use.

How To Fix

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

npm uninstall react-sdkk

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