CVE-MAL-2022-653: Malicious code in @tinkoff-react-bui/dropdown (npm)

@tinkoff-react-bui/dropdown Updated 02 Oct 2025

Summary

20/06/2022
CRITICAL
No i
Critical
Not published

MAL-2022-653: Malicious code in @tinkoff-react-bui/dropdown (npm). Affected versions are not published. 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 @tinkoff-react-bui/dropdown package is an npm package that provides dropdown functionality for React applications. It is commonly used to create dropdown menus and select components in web applications. This package is vulnerable to a malicious code injection attack, which can compromise the security of the host system and expose sensitive information.

Vulnerability Detail

The vulnerability originates from the presence of malicious code in the @tinkoff-react-bui/dropdown package. This code can be executed on any system that has the package installed or running, leading to a complete compromise of the system. As a result, all secrets and keys stored on the affected system should be rotated immediately from a different computer. Removing the package may not guarantee the removal of all malicious software installed as a result of its installation. The impact of this vulnerability can be severe, potentially leading to unauthorized access, data breaches, and other malicious activities.

How To Fix

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

npm uninstall @tinkoff-react-bui/dropdown

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

There is no specific workaround available for this vulnerability. It is crucial to follow the steps mentioned in the 'how_to_fix' section to mitigate the risk and ensure the security of the affected systems.

Conclusion

The @tinkoff-react-bui/dropdown package is vulnerable to a malicious code injection attack, which can lead to a complete compromise of the affected system. It is crucial to take immediate action by following the steps mentioned in the 'how_to_fix' section to mitigate the risk and ensure the security of the systems. For further support on vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for @tinkoff-react-bui/dropdown →

Share this vulnerability

FAQ

This vulnerability can lead to a complete compromise of the affected system, potentially resulting in unauthorized access, data breaches, and other malicious activities.

You can use the Vulert Playground (https://vulert.com/scanner) to check if your application is affected by this vulnerability. It analyzes the package-lock.json file to monitor and alert in real-time for open-source vulnerabilities.

If your system is affected, it is recommended to follow the steps mentioned in the 'how_to_fix' section to remediate the vulnerability and ensure the security of your system.

Removing the package is a necessary step to mitigate the risk, but it may not guarantee the removal of all malicious software installed as a result of its installation. A thorough security audit should be conducted to ensure the system is free from any other malicious software.

It is recommended to search for alternative packages that provide similar functionality and have a good security track record. Conduct thorough research and consider the popularity, community support, and security practices of the alternative packages before making a decision.

How To Fix

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

npm uninstall @tinkoff-react-bui/dropdown

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