Which versions of b2b-common-cb-lib are malicious?

The following npm versions of b2b-common-cb-lib are flagged malicious: 99.99.99, 100.0.0. Treat any of these as compromised.

How do I remediate b2b-common-cb-lib if I installed it?

Remove b2b-common-cb-lib 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 b2b-common-cb-lib — how do I know if it already compromised me?

If b2b-common-cb-lib was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.

Is b2b-common-cb-lib part of a known attack campaign?

Yes — b2b-common-cb-lib is associated with the GHSA-3g6j-9975-jm52, RLMA-2026-01113, RLUA-2026-01713 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 b2b-common-cb-lib across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for b2b-common-cb-lib (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging b2b-common-cb-lib across your stack and pipelines.

Malicious package

b2b-common-cb-libnpm

Malicious code in b2b-common-cb-lib (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-1356

Immediate action

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

npm uninstall b2b-common-cb-lib

What this malware does

The package b2b-common-cb-lib was found to contain malicious code.

Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

Malicious versions

2 flagged

99.99.99100.0.0

Indicators of compromise (SHA-256)

dc8b9e7f3335ea007ff8c1eebca88d692c9bbfbbd22d5890807889ef4b6ad952

6a9c7773c54e6a203f72c6329dcdc72bf8937d199f854302313712232c51882d

a0699be4242e2a015c76aad1b5ee1f2482f01a59017778511108ed33b8729a8e

4be9ab9a85cddbb674ba26d2e8251a7b09d563711643c12894844a9e34ac8330

Detection & response playbook

Malicious package

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for b2b-common-cb-lib (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging b2b-common-cb-lib across your stack and pipelines.
If you installed it — respond
Remove b2b-common-cb-lib 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 b2b-common-cb-lib was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks b2b-common-cb-lib before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.

Frequently asked questions

No. b2b-common-cb-lib on npm has been identified as a malicious package (versions 99.99.99, 100.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-3g6j-9975-jm52RLMA-2026-01113RLUA-2026-01713

References

github.com

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks b2b-common-cb-lib-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