Which versions of @cbreone/core-ui are malicious?

The following npm versions of @cbreone/core-ui are flagged malicious: 999.999.999, 9999.9999.9999. Treat any of these as compromised.

How do I remediate @cbreone/core-ui if I installed it?

Remove @cbreone/core-ui from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

I already installed @cbreone/core-ui — how do I know if it already compromised me?

If @cbreone/core-ui was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Is @cbreone/core-ui part of a known attack campaign?

Yes — @cbreone/core-ui is associated with the RLMA-2026-00972 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find @cbreone/core-ui across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for @cbreone/core-ui (2 malicious versions).

Malicious package

@cbreone/core-uinpm

Advisory published Mar 18, 2026Updated Mar 23, 2026

@cbreone/core-ui is a confirmed malicious npm package (MAL-2026-1590) that executes malicious code on install (malicious versions 999.999.999, 9999.9999.9999). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @cbreone/core-ui (npm)

MAL-2026-1590

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall @cbreone/core-ui

What this malware does

The package @cbreone/core-ui was found to contain malicious code.

Malicious versions

2 flagged

999.999.9999999.9999.9999

Indicators of compromise (SHA-256)

c7ca64da3e0323606f789927e9998492f038a5d80c6647bede9c6ad2fe184b0b

b7e204888ba2b9573e474d804f28f51173684bb25f640615a9eaae217c5e1a45

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for @cbreone/core-ui (2 malicious versions).
If you installed it — respond
Remove @cbreone/core-ui from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If @cbreone/core-ui was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. @cbreone/core-ui on npm has been identified as a malicious package (versions 999.999.999, 9999.9999.9999 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2026-00972

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks @cbreone/core-ui-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database