Which versions of bridgebbb are malicious?

The following RubyGems versions of bridgebbb are flagged malicious: 0.0.1. Treat any of these as compromised.

How do I remediate bridgebbb if I installed it?

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

If bridgebbb 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 bridgebbb part of a known attack campaign?

Yes — bridgebbb is associated with the RLMA-2026-02204 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 bridgebbb across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for bridgebbb (version 0.0.1).

Malicious package

bridgebbbRubyGems

Advisory published Jul 7, 2026Updated Jul 23, 2026

bridgebbb is a confirmed malicious RubyGems package (MAL-2026-7553) that executes malicious code on install (malicious version 0.0.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in bridgebbb (RubyGems)

MAL-2026-7553

Immediate action

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

gem uninstall bridgebbb

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

b022f2a57fb16c49c5db51f1e3f07b377a70b0f242d0d1d2f983af11a25e5ffc

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for bridgebbb (version 0.0.1).
If you installed it — respond
Remove bridgebbb 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 bridgebbb 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. bridgebbb on RubyGems has been identified as a malicious package (version 0.0.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2026-02204

Credits

ReversingLabs · finder

Detect & block this

O3 blocks bridgebbb-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