Critical Malicious Code Vulnerability in supabase-react Package

supabase-react Updated 02 Oct 2025

Summary

10/07/2025
CRITICAL
No i
Critical
Not published

MAL-2025-5797: Malicious code in supabase-react (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 supabase-react package is a popular library used for integrating Supabase with React applications, providing developers with tools to manage authentication, database interactions, and real-time subscriptions. However, this package has been identified to contain malicious code that compromises the security of any system it is installed on, making it crucial for developers to be aware of this vulnerability.

Vulnerability Detail

The vulnerability originates from embedded malicious code within the supabase-react package. This code can fully compromise any computer that has the package installed, potentially allowing unauthorized access to sensitive information such as secrets and keys. The presence of this malicious code poses significant risks, including data breaches and unauthorized control over affected systems.

How To Fix

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

npm uninstall supabase-react

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 temporary measure, you can prevent the use of the compromised package by removing it from your dependencies and replacing it with an alternative library that provides similar functionality. Ensure to audit your codebase for any references to supabase-react and remove them accordingly.

Conclusion

The supabase-react package has been identified as containing malicious code that poses a significant security risk. Immediate action is required to remove the package and secure any affected systems. Developers should remain vigilant and utilize tools like Vulert to monitor for vulnerabilities in their applications.

See every vulnerability recorded for supabase-react →

Share this vulnerability

FAQ

Immediately uninstall the package and rotate any secrets or keys stored on the affected 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.

Currently, there is no patch available, and it is recommended to remove the package until a secure version is released.

Failure to address this vulnerability can lead to unauthorized access to sensitive data and complete control over your system by malicious actors.

It is advisable to monitor the package's repository for updates and community feedback before considering its use again.

How To Fix

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

npm uninstall supabase-react

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