Malicious Code Detected in ch-react-help Package

ch-react-help Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-16752: Malicious code in ch-react-help (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 ch-react-help package is an npm library designed to assist developers in integrating React components with helpful utilities. It is commonly used in web applications to enhance user experience. However, recent findings have revealed that this package contains malicious code, posing significant risks to applications that utilize it.

Vulnerability Detail

The vulnerability in the ch-react-help package stems from the inclusion of malicious code that can compromise the security of applications using this library. This code may lead to unauthorized access, data breaches, or other harmful actions within the affected systems. The issue was introduced in version 0 and affects all subsequent versions.

How To Fix

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

npm uninstall ch-react-help

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 avoid using the ch-react-help package and seek alternative libraries that provide similar functionality without the associated risks. Ensure to review the security status of any new packages before integrating them into your project.

Conclusion

The discovery of malicious code in the ch-react-help package poses a serious threat to applications that utilize it. Developers are advised to uninstall the package and monitor for updates or patches. Utilizing tools like Vulert can help keep your projects secure by providing real-time alerts for vulnerabilities.

See every vulnerability recorded for ch-react-help →

Share this vulnerability

FAQ

ch-react-help is an npm library that provides utilities for integrating React components into web applications.

The malicious code can lead to unauthorized access and potential data breaches within applications using the ch-react-help package.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software. Check your application against the vulnerability using the Vulert playground at Vulert Scanner.

Currently, there is no patched version available. It is recommended to uninstall the package until a secure version is released.

Uninstall the ch-react-help package immediately and consider using alternative libraries that do not have known vulnerabilities.

How To Fix

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

npm uninstall ch-react-help

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