Which versions of biubdler are malicious?

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

How do I remediate biubdler if I installed it?

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

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

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

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

Malicious package

biubdlerRubyGems

Advisory published Sep 22, 2026Updated Sep 24, 2026

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

Malicious code in biubdler (RubyGems)

MAL-2026-16614

Immediate action

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

gem uninstall biubdler

Malicious versions

2 flagged

1.0.01.0.82145

Indicators of compromise (SHA-256)

d5e223a09602659b31fdf480a3aa5ecf2f25dfb11e5adced73d550afbc9cbf9a

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-07278

Credits

ReversingLabs · finder

Detect & block this

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