Malicious Code Vulnerability in @emerald-react/badge Package

@emerald-react/badge Updated 19 Mar 2026

Summary

18/03/2026
CRITICAL
No i
Critical
Not published

MAL-2026-1599: Malicious code in @emerald-react/badge (npm). Affects @emerald-react/badge 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/badge package is a component library for React applications, providing customizable badge components for displaying status or notifications. It is widely used in various web applications due to its ease of integration and flexibility. However, this package has been identified to contain malicious code, posing significant security risks to applications that utilize it.

Vulnerability Detail

The vulnerability in the @emerald-react/badge package stems from the inclusion of malicious code that can compromise the security of applications using this package. This code may lead to unauthorized access, data leakage, or other malicious activities. The issue was reported by ReversingLabs, and it affects specific versions of the package, making it crucial for developers to take immediate action to mitigate potential risks.

How To Fix

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

npm uninstall @emerald-react/badge

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

If immediate updating is not feasible, consider removing the @emerald-react/badge package from your project until a secure version is available. You can do this by running: npm uninstall @emerald-react/badge.

Conclusion

The @emerald-react/badge package has been identified to contain malicious code, posing a significant security risk to applications. It is essential for developers to update the package to a secure version or remove it until a fix is available. Monitoring tools like Vulert can assist in identifying vulnerabilities in your projects.

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

Share this vulnerability

FAQ

The malicious code can potentially allow unauthorized access to sensitive data within applications that use this package.

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

Consider removing the @emerald-react/badge package from your project until a secure version is available.

The vulnerability was reported by ReversingLabs, a security research firm specializing in malware analysis.

While specific exploits have not been detailed, the presence of malicious code indicates a high risk of exploitation.

How To Fix

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

npm uninstall @emerald-react/badge

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