Which versions of bunadler are malicious?

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

How do I remediate bunadler if I installed it?

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

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

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

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

Malicious package

bunadlerRubyGems

Advisory published Sep 22, 2026Updated Sep 24, 2026

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

Malicious code in bunadler (RubyGems)

MAL-2026-16898

Immediate action

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

gem uninstall bunadler

Malicious versions

2 flagged

1.0.01.0.17618

Indicators of compromise (SHA-256)

d70c7c8b117b0c7ba2c0c800a453e0696417b3a60dcbd4a186d011575b0fe2fc

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-07584

Credits

ReversingLabs · finder

Detect & block this

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