Malicious Code Detected in @tui-react-internal/select-account-icon Package

Summary

10/07/2025
CRITICAL
No i
Critical
Not published

MAL-2025-5803: Malicious code in @tui-react-internal/select-account-icon (npm). Affects @tui-react-internal/select-account-icon versions >= 1.99.99. 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 @tui-react-internal/select-account-icon package is an npm library designed for React applications, providing a selection icon component for user accounts. While it offers useful functionality for developers, it has been identified as having a serious security vulnerability that allows it to communicate with a domain associated with malicious activities.

Vulnerability Detail

The vulnerability arises from the package's ability to connect to a malicious domain, potentially leading to data breaches, unauthorized access, or other security threats. This issue was introduced in version 1.99.99 and poses significant risks to applications utilizing this package, as it may compromise user data and application integrity.

How To Fix

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

npm uninstall @tui-react-internal/select-account-icon

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 an immediate update is not feasible, consider removing the package from your project until a secure version is available. You can do this by executing: npm uninstall @tui-react-internal/select-account-icon.

Conclusion

The @tui-react-internal/select-account-icon package has been identified with a serious vulnerability that allows communication with a malicious domain. It is crucial for developers to update the package or remove it from their projects to ensure the security of their applications.

See every vulnerability recorded for @tui-react-internal/select-account-icon →

Share this vulnerability

FAQ

The vulnerability allows the package to communicate with a domain linked to malicious activities, posing risks to user data.

You can use Vulert, which monitors open-source vulnerabilities in your software. Simply upload your package-lock.json file to receive real-time alerts.

Yes, updating to a patched version of the @tui-react-internal/select-account-icon package will resolve the vulnerability.

As a temporary measure, you can uninstall the package to mitigate risks until a secure version is available.

Detailed information can be found in the vulnerability report on GitHub and through security advisories related to the npm ecosystem.

How To Fix

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

npm uninstall @tui-react-internal/select-account-icon

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