Which versions of bubdler are malicious?

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

How do I remediate bubdler if I installed it?

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

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

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

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

Malicious package

bubdlerRubyGems

Advisory published Sep 22, 2026Updated Sep 24, 2026

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

Malicious code in bubdler (RubyGems)

MAL-2026-16774

Immediate action

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

gem uninstall bubdler

Malicious versions

2 flagged

1.0.01.0.68402

Indicators of compromise (SHA-256)

3f2a26eee9baf3d5de2d46f9d5e551b5bfa6f95e7f25db2038184963f12ad604

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-07459

Credits

ReversingLabs · finder

Detect & block this

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