Critical Malicious Code Vulnerability in @myop/react Package

@myop/react Updated 02 Oct 2025

Summary

12/05/2025
CRITICAL
No i
Critical
Not published

MAL-2025-3750: Malicious code in @myop/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 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 @myop/react package is a JavaScript library used within the npm ecosystem, primarily for building user interfaces in React applications. It offers various functionalities that enhance the development experience. However, this package has been identified as containing malicious code, posing significant risks to any system utilizing it.

Vulnerability Detail

The vulnerability stems from the presence of embedded malicious code within the @myop/react 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 the malicious package identified by the GitHub Security Advisory (GHSA-5xpx-gq89-872x). Users are advised that simply removing the package may not eliminate all traces of the malicious software, as full control of the affected computer may have been granted to an external entity.

How To Fix

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

npm uninstall @myop/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

There are no effective workarounds for this vulnerability other than removing the package and securing the system. It is essential to ensure that all sensitive information is rotated and that the system is monitored for any further malicious activity.

Conclusion

The @myop/react package has been identified as containing malicious code, posing significant risks to users and their systems. Immediate action is required to remove the package and secure any sensitive information. Users are encouraged to monitor their systems closely and utilize tools like Vulert for ongoing vulnerability management.

See every vulnerability recorded for @myop/react →

Share this vulnerability

FAQ

Immediately remove the package and rotate any sensitive information stored on the affected system.

You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.

No, it is not safe. The presence of malicious code means your application and system are at risk.

The consequences include unauthorized access to sensitive data, potential data breaches, and loss of control over the affected system.

Not necessarily. While removing the package is crucial, there may still be residual malicious software that could pose a threat.

How To Fix

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

npm uninstall @myop/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