Which versions of bunelder are malicious?

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

How do I remediate bunelder if I installed it?

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

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

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

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

Malicious package

bunelderRubyGems

Advisory published Sep 22, 2026Updated Sep 24, 2026

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

Malicious code in bunelder (RubyGems)

MAL-2026-17024

Immediate action

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

gem uninstall bunelder

Malicious versions

2 flagged

1.0.01.0.70043

Indicators of compromise (SHA-256)

d132d1d304cfd6dd991d8293a044e8d40fcb2455e6c9370860a6e624ec5981f5

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-07710

Credits

ReversingLabs · finder

Detect & block this

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