Critical Malicious Activity Detected in recoil-shared Package

recoil-shared Updated 02 Oct 2025

Summary

13/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-6953: Malicious code in recoil-shared (npm). Affects recoil-shared versions >= 1.0.0. 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

The recoil-shared package is a JavaScript library used in React applications for state management. It allows developers to manage shared state across components efficiently. However, this package has been identified to communicate with a domain associated with malicious activities, posing a significant risk to applications that utilize it.

Vulnerability Detail

The vulnerability in the recoil-shared package arises from its communication with a domain linked to malicious activities. This could potentially lead to data breaches, unauthorized access, or the execution of harmful code within applications that depend on this package. The issue was introduced in version 1.0.0 and has been classified as a serious security threat.

How To Fix

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

npm uninstall recoil-shared

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 workaround, you can remove the recoil-shared package from your project until a secure version is released. You can do this by executing: npm uninstall recoil-shared. This will prevent any potential malicious activity while you await a fix.

Conclusion

The recoil-shared package has been identified as having a serious vulnerability due to its communication with a malicious domain. It is crucial for developers using this package to take immediate action by updating or uninstalling it to protect their applications from potential threats.

See every vulnerability recorded for recoil-shared →

Share this vulnerability

FAQ

Recoil-shared is a JavaScript library for state management in React applications, allowing efficient sharing of state across components.

The package communicates with a domain known for malicious activities, which could lead to data breaches or unauthorized access.

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

It is recommended to check for the latest version of the recoil-shared package and update it to ensure you have the latest security fixes.

As a temporary measure, consider uninstalling the recoil-shared package to prevent any potential malicious activity until a secure version is available.

How To Fix

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

npm uninstall recoil-shared

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