Which versions of bunrdler are malicious?

The following RubyGems versions of bunrdler are flagged malicious: 1.0.26539. Treat any of these as compromised.

How do I remediate bunrdler if I installed it?

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

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

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

Search your lockfiles and build artifacts for bunrdler (version 1.0.26539).

Malicious package

bunrdlerRubyGems

Advisory published Sep 22, 2026Updated Sep 24, 2026

bunrdler is a confirmed malicious RubyGems package (MAL-2026-17115) that executes malicious code on install (malicious version 1.0.26539). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in bunrdler (RubyGems)

MAL-2026-17115

Immediate action

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

gem uninstall bunrdler

Malicious versions

1 flagged

1.0.26539

Indicators of compromise (SHA-256)

7a93f88d791110d58fc1af6c22f49e3d843cb0c431ea7ba64e13fbb7a8cf03e2

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-07801

Credits

ReversingLabs · finder

Detect & block this

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