Malicious Code Vulnerability in @emerald-react/input Package

@emerald-react/input Updated 19 Mar 2026

Summary

18/03/2026
CRITICAL
No i
Critical
Not published

MAL-2026-1612: Malicious code in @emerald-react/input (npm). Affects @emerald-react/input 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 MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

The @emerald-react/input package is a component library for React applications, providing input elements with customizable features and styles. It is widely used in various projects to enhance user interface interactions. However, this package has been identified to contain malicious code, posing a significant risk to applications that utilize it.

Vulnerability Detail

The vulnerability originates from malicious code embedded within the @emerald-react/input package. This code can potentially compromise the security of applications by executing unauthorized actions, leading to data breaches or unauthorized access. The affected versions include '999.999.999' and '9999.9999.999', which are known to contain this malicious code.

How To Fix

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

npm uninstall @emerald-react/input

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, consider removing the @emerald-react/input package from your project until a secure version is released. You can do this by running the command: npm uninstall @emerald-react/input.

Conclusion

The @emerald-react/input package has a critical vulnerability due to malicious code that can compromise application security. It is crucial to update to a secure version or remove the package until a fix is available. Utilizing tools like Vulert can help monitor your application for vulnerabilities effectively.

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

Share this vulnerability

FAQ

The malicious code can execute unauthorized actions within applications, potentially leading to data breaches.

You can use Vulert to monitor and alert for open-source vulnerabilities in your software. Visit Vulert Scanner to check your application without needing to sign up.

The affected versions include '999.999.999' and '9999.9999.999'.

Yes, updating to the latest version of the @emerald-react/input package will help mitigate the vulnerability.

As a temporary measure, consider uninstalling the package 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 @emerald-react/input

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