Malicious Code Vulnerability in @emerald-react/button Package

@emerald-react/button Updated 19 Mar 2026

Summary

18/03/2026
CRITICAL
No i
Critical
Not published

MAL-2026-1601: Malicious code in @emerald-react/button (npm). Affects @emerald-react/button versions 999.999.999 – 9999.9999.9999. 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 @emerald-react/button package is a component library for React applications, providing customizable button components for user interfaces. It is widely used for its ease of integration and flexibility in design. However, this package has been identified with a serious vulnerability that could allow malicious code execution, posing a risk to applications that rely on it.

Vulnerability Detail

The vulnerability in the @emerald-react/button package stems from the inclusion of malicious code that can compromise the security of applications using this package. This issue was reported by ReversingLabs and affects specific versions of the package. If exploited, it could lead to unauthorized access, data breaches, and other security incidents. The malicious code is embedded in the package, making it difficult for users to detect without thorough inspection.

How To Fix

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

npm uninstall @emerald-react/button

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 remove the @emerald-react/button package from your project until a secure version is available. Use the following command to uninstall the package: npm uninstall @emerald-react/button. Consider using alternative button component libraries in the meantime.

Conclusion

The @emerald-react/button package has a critical vulnerability due to malicious code that can compromise application security. Users are advised to update to the latest version or remove the package until a fix is implemented. Utilizing tools like Vulert can help monitor and identify vulnerabilities in your projects effectively.

See every vulnerability recorded for @emerald-react/button →

Share this vulnerability

FAQ

The vulnerability involves malicious code that can execute unauthorized actions within applications using the package.

You can use Vulert, which monitors open-source vulnerabilities in your software by analyzing the package-lock.json file. Visit Vulert Scanner to check your application without needing to sign up.

If an immediate update is not possible, consider removing the package from your project and using alternative libraries until a secure version is released.

The vulnerability was reported by ReversingLabs, a cybersecurity firm specializing in threat intelligence.

Yes, the affected versions include 999.999.999 and 9999.9999.9999. It is crucial to update to a version that does not contain this vulnerability.

How To Fix

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

npm uninstall @emerald-react/button

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