Which versions of bunrlder are malicious?

The following RubyGems versions of bunrlder are flagged malicious: 1.0.8611. Treat any of these as compromised.

How do I remediate bunrlder if I installed it?

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

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

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

Search your lockfiles and build artifacts for bunrlder (version 1.0.8611).

Malicious package

bunrlderRubyGems

Advisory published Sep 22, 2026Updated Sep 24, 2026

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

Malicious code in bunrlder (RubyGems)

MAL-2026-17116

Immediate action

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

gem uninstall bunrlder

Malicious versions

1 flagged

1.0.8611

Indicators of compromise (SHA-256)

34c651266cec4698fbb67423ba0ec3a2a7003ce2a561e7f7a0fc19174e9efead

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-07802

Credits

ReversingLabs · finder

Detect & block this

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