Malicious Code Detected in @cbreone/core-ui: Security Alert

@cbreone/core-ui Updated 19 Mar 2026

Summary

18/03/2026
CRITICAL
No i
Critical
Not published

MAL-2026-1590: Malicious code in @cbreone/core-ui (npm). Affects @cbreone/core-ui 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 @cbreone/core-ui package is a component library designed for building user interfaces in web applications. It provides a set of reusable UI components that help developers create visually appealing and functional web applications efficiently. However, this package has been identified as containing malicious code that could compromise the security of applications utilizing it.

Vulnerability Detail

The vulnerability in the @cbreone/core-ui package stems from the inclusion of malicious code that can potentially execute harmful actions within the user's environment. This issue was reported by ReversingLabs and affects specific versions of the package. The malicious code can lead to unauthorized access, data breaches, or other security incidents, making it critical for users to address this vulnerability promptly.

How To Fix

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

npm uninstall @cbreone/core-ui

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

As a temporary workaround, users can remove the @cbreone/core-ui package from their project until a secure version is released. This can be done using the command: npm uninstall @cbreone/core-ui.

Conclusion

The @cbreone/core-ui package has been identified as containing malicious code that poses a significant security risk. Users are strongly advised to update the package to a secure version or remove it from their projects until a fix is available. Utilizing tools like Vulert can help monitor and manage vulnerabilities effectively.

See every vulnerability recorded for @cbreone/core-ui →

Share this vulnerability

FAQ

The malicious code is designed to execute harmful actions that can compromise the security of applications using the package.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software. Visit the Vulert playground at Vulert Scanner to check your application without any signup.

If an immediate update is not possible, consider removing the package as a temporary measure to mitigate risks.

Yes, the affected versions include 999.999.999 and 9999.9999.9999 as reported by ReversingLabs.

For more information, you can reach out to ReversingLabs through their website at https://www.reversinglabs.com.

How To Fix

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

npm uninstall @cbreone/core-ui

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