Which versions of bunader are malicious?

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

How do I remediate bunader if I installed it?

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

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

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

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

Malicious package

bunaderRubyGems

Advisory published Sep 22, 2026Updated Sep 24, 2026

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

Malicious code in bunader (RubyGems)

MAL-2026-16896

Immediate action

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

gem uninstall bunader

Malicious versions

2 flagged

1.0.01.0.83765

Indicators of compromise (SHA-256)

b6b6c541bb89d1a5e57348660a57e4523e3c7478aad9d1bffa0d2c450fa6d731

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-07582

Credits

ReversingLabs · finder

Detect & block this

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