Which versions of bublder are malicious?

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

How do I remediate bublder if I installed it?

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

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

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

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

Malicious package

bublderRubyGems

Advisory published Sep 22, 2026Updated Sep 24, 2026

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

Malicious code in bublder (RubyGems)

MAL-2026-16775

Immediate action

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

gem uninstall bublder

Malicious versions

2 flagged

1.0.01.0.62205

Indicators of compromise (SHA-256)

de103ac1c350a4909004c55b5643a6ca436a86e176c4d97365a393edfa178b5d

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-07460

Credits

ReversingLabs · finder

Detect & block this

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