Which versions of bbusndler are malicious?

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

How do I remediate bbusndler if I installed it?

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

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

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

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

Malicious package

bbusndlerRubyGems

Advisory published Sep 22, 2026Updated Sep 24, 2026

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

Malicious code in bbusndler (RubyGems)

MAL-2026-16576

Immediate action

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

gem uninstall bbusndler

Malicious versions

2 flagged

1.0.01.0.78071

Indicators of compromise (SHA-256)

89c8807277bf6dae61e1680febd72a8c5b9a96cc51991267d323c8457d810912

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-07224

Credits

ReversingLabs · finder

Detect & block this

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