Critical Malicious Code Vulnerability in @kui-react/button Package

@kui-react/button Updated 19 Mar 2026

Summary

18/03/2026
CRITICAL
No i
Critical
Not published

MAL-2026-1625: Malicious code in @kui-react/button (npm). Affects @kui-react/button versions 9.9.9 – 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 Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The @kui-react/button package is a component library for building user interface buttons in React applications. It provides developers with customizable button components that enhance user experience. However, this package has been found to contain malicious code, posing significant security risks to applications that utilize it.

Vulnerability Detail

The vulnerability originates from malicious code embedded within specific versions of the @kui-react/button package. This code can lead to unauthorized access, data breaches, or other harmful actions within applications that depend on this package. The affected versions include 9.9.9, 999.999.999, and 9999.9999.999, which are known to be compromised. Developers using these versions are at risk of exploitation.

How To Fix

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

npm uninstall @kui-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

If immediate updating is not feasible, consider removing the @kui-react/button package from your project until a secure version is available. You can do this by running: npm uninstall @kui-react/button. Alternatively, you may replace it with a different button component library that is known to be secure.

Conclusion

The @kui-react/button package has been identified as containing malicious code, posing a serious threat to applications that utilize it. Developers are urged to update to a secure version or implement workarounds to mitigate risks. Regular monitoring for vulnerabilities is essential to maintain application security.

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

Share this vulnerability

FAQ

The malicious code can perform unauthorized actions within applications, potentially leading to data breaches or system compromises.

Check your package-lock.json file for the version of @kui-react/button. If it matches 9.9.9, 999.999.999, or 9999.9999.999, your application is affected.

Yes, you can use Vulert, which monitors and alerts for open-source vulnerabilities in your software using just package-lock.json. Visit vulert.com for more information.

Consider removing the package or replacing it with a secure alternative until you can update to a patched version.

Detailed information can be found on the GitHub repository of the malicious packages, specifically at the provided source link.

How To Fix

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

npm uninstall @kui-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