Which versions of bbiundler are malicious?

The following RubyGems versions of bbiundler are flagged malicious: 1.0.0, 1.0.93989. Treat any of these as compromised.

How do I remediate bbiundler if I installed it?

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

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

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

Search your lockfiles and build artifacts for bbiundler (2 malicious versions).

Malicious package

bbiundlerRubyGems

Advisory published Sep 22, 2026Updated Sep 24, 2026

bbiundler is a confirmed malicious RubyGems package (MAL-2026-16571) that executes malicious code on install (malicious versions 1.0.0, 1.0.93989). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in bbiundler (RubyGems)

MAL-2026-16571

Immediate action

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

gem uninstall bbiundler

Malicious versions

2 flagged

1.0.01.0.93989

Indicators of compromise (SHA-256)

7d8503c5b6acaea3b75a9ee4fbdad33b84e0bc36c12746f837f85fbf6f539284

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-07218

Credits

ReversingLabs · finder

Detect & block this

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