Critical Malicious Code Vulnerability in react-count-sync Package

react-count-sync Updated 05 Feb 2026

Summary

04/02/2026
CRITICAL
No i
Critical
Not published

MAL-2026-746: Malicious code in react-count-sync (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

The react-count-sync package is a utility for synchronizing counts in React applications, allowing developers to manage state effectively across components. However, this package has been identified as containing malicious code that compromises the security of any system where it is installed. The vulnerability poses a significant risk as it can lead to unauthorized access and control over the affected systems.

Vulnerability Detail

The vulnerability originates from the inclusion of malicious code within the react-count-sync package. This code can fully compromise any computer that has the package installed, allowing external entities to gain control over the system. The ramifications include potential data breaches, loss of sensitive information, and unauthorized access to secrets and keys stored on the compromised computer. The technical aspect of this vulnerability is classified under CWE-506, which indicates that the product contains embedded malicious code.

How To Fix

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

npm uninstall react-count-sync

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

There are no effective workarounds for this vulnerability other than removing the package and securing the system. Ensure that all sensitive data is rotated and monitored for any unauthorized access.

Conclusion

The react-count-sync 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 sensitive information. Utilizing tools like Vulert can help prevent similar vulnerabilities in the future.

See every vulnerability recorded for react-count-sync →

Share this vulnerability

FAQ

Immediately uninstall the react-count-sync package and rotate any sensitive information 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.

Leaving the react-count-sync package installed can lead to unauthorized access to your system, data breaches, and the potential for malicious actors to control your computer.

Regularly monitor your dependencies for vulnerabilities using tools like Vulert, which can alert you in real-time for open-source vulnerabilities.

Vulert monitors and alerts for open-source vulnerabilities in your software using just the package-lock.json file, providing real-time insights into potential risks.

How To Fix

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

npm uninstall react-count-sync

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