Which versions of bunsdler are malicious?

The following RubyGems versions of bunsdler are flagged malicious: 1.0.76068. Treat any of these as compromised.

How do I remediate bunsdler if I installed it?

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

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

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

Search your lockfiles and build artifacts for bunsdler (version 1.0.76068).

Malicious package

bunsdlerRubyGems

Advisory published Sep 22, 2026Updated Sep 24, 2026

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

Malicious code in bunsdler (RubyGems)

MAL-2026-17120

Immediate action

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

gem uninstall bunsdler

Malicious versions

1 flagged

1.0.76068

Indicators of compromise (SHA-256)

0538ed72e81d91e2d6527f020e780edb63670605f09e21f8adeeee6e9f799b46

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-07806

Credits

ReversingLabs · finder

Detect & block this

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