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

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

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

Remove @cbreone/core-services 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-services — how do I know if it already compromised me?

If @cbreone/core-services 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-services part of a known attack campaign?

Yes — @cbreone/core-services is associated with the RLMA-2026-00971 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-services across my projects, lockfiles, and CI pipelines?

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

Malicious package

@cbreone/core-servicesnpm

Advisory published Mar 18, 2026Updated Mar 23, 2026

@cbreone/core-services is a confirmed malicious npm package (MAL-2026-1589) 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-services (npm)

MAL-2026-1589

Immediate action

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

npm uninstall @cbreone/core-services

What this malware does

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

Malicious versions

2 flagged

999.999.9999999.9999.9999

Indicators of compromise (SHA-256)

ec18bfdff24671f5b9d47c987956bcc88f6927672f4b654b00501773b1c3cb37

7ae6ae37b27a798985e4dcf5adf27c7fe173717d253c4fab67acf96656bb9f8b

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for @cbreone/core-services (2 malicious versions).
If you installed it — respond
Remove @cbreone/core-services 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-services 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-services 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-00971

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks @cbreone/core-services-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