Malicious code in brkr-lib-components-react (npm)

brkr-lib-components-react Updated 02 Oct 2025

Summary

25/06/2024
CRITICAL
No i
Critical
Not published

MAL-2024-1841: Malicious code in brkr-lib-components-react (npm). Affects brkr-lib-components-react versions 100.0.0. 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 brkr-lib-components-react package is an open-source library for building React components. It provides a set of reusable UI components that can be used to create user interfaces in React applications. The package is commonly used in web development projects and is available on the npm registry. However, the package has been found to contain malicious code, which poses a security risk to applications that depend on it.

Vulnerability Detail

The vulnerability in brkr-lib-components-react is due to the presence of malicious code in the package. This code can be exploited by attackers to perform various malicious activities, such as stealing sensitive information, executing arbitrary code, or compromising the security of the application. The malicious code was discovered by ReversingLabs and has been reported as a high-risk vulnerability. The affected version of the package is 100.0.0.

How To Fix

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

npm uninstall brkr-lib-components-react

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 mentioned for this vulnerability. The best course of action is to update the package to a non-malicious version as mentioned in the 'how_to_fix' section.

Conclusion

The brkr-lib-components-react package has been found to contain malicious code, posing a significant security risk to applications that depend on it. It is crucial for developers to update to a non-malicious version and review the package's source code and dependencies for any other potential security issues. Regularly monitoring for security advisories and staying updated with patches is essential to maintain the security of the application.

See every vulnerability recorded for brkr-lib-components-react →

Share this vulnerability

FAQ

brkr-lib-components-react is an open-source library for building React components. It provides a set of reusable UI components that can be used in React applications.

The vulnerability allows attackers to exploit the malicious code in the brkr-lib-components-react package, potentially leading to unauthorized access, data theft, or compromise of the application's security.

You can use the Vulert Playground at Vulert Scanner to check if your application is affected by this vulnerability. Simply provide your package-lock.json file, and Vulert will analyze it in real-time.

Yes, the recommended fix is to update the brkr-lib-components-react package to a non-malicious version. Avoid using version 100.0.0 and upgrade to a newer version that has been verified to be free of malicious code.

It is advisable to review the package's source code and dependencies for any other potential security issues. Additionally, staying updated with the latest security advisories and patches is crucial to ensure the overall security of the application.

How To Fix

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

npm uninstall brkr-lib-components-react

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