Malicious Code Vulnerability in @cbreone/utilities Package

@cbreone/utilities Updated 19 Mar 2026

Summary

18/03/2026
CRITICAL
No i
Critical
Not published

MAL-2026-1593: Malicious code in @cbreone/utilities (npm). Affects @cbreone/utilities 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 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 @cbreone/utilities package is a utility library designed for use in JavaScript applications, providing various functions to enhance development efficiency. However, it has been identified as containing malicious code that poses significant security risks to applications that utilize it.

Vulnerability Detail

The vulnerability stems from malicious code embedded within the @cbreone/utilities package. This code can potentially compromise the security of applications by allowing unauthorized access or manipulation of data. The affected versions are 999.999.999 and 9999.9999.9999, which have been flagged for containing this harmful code. Users of this package should be aware of the risks associated with using these versions, as they may lead to data breaches or other security incidents.

How To Fix

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

npm uninstall @cbreone/utilities

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, you can remove the @cbreone/utilities package from your project until a secure version is released. This can be done by running the following command: npm uninstall @cbreone/utilities.

Conclusion

The @cbreone/utilities package has a serious vulnerability due to the presence of malicious code. Users are strongly advised to update to a secure version or remove the package from their projects until a fix is available. Utilizing tools like Vulert can help monitor for such vulnerabilities in real-time.

See every vulnerability recorded for @cbreone/utilities →

Share this vulnerability

FAQ

The malicious code can allow unauthorized access to application data, potentially leading to data breaches.

You can use Vulert to monitor and alert for open-source vulnerabilities in your software. Visit Vulert Scanner to check if your application is affected without needing to sign up.

If an immediate update is not possible, consider removing the package from your project as a temporary measure.

Versions other than 999.999.999 and 9999.9999.9999 are considered safe, but always check for the latest updates.

The vulnerability was identified by ReversingLabs, a security research firm.

How To Fix

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

npm uninstall @cbreone/utilities

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