Which versions of bunldoer are malicious?

The following RubyGems versions of bunldoer are flagged malicious: 1.0.73882. Treat any of these as compromised.

How do I remediate bunldoer if I installed it?

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

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

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

Search your lockfiles and build artifacts for bunldoer (version 1.0.73882).

Malicious package

bunldoerRubyGems

Advisory published Sep 22, 2026Updated Sep 24, 2026

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

Malicious code in bunldoer (RubyGems)

MAL-2026-17075

Immediate action

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

gem uninstall bunldoer

Malicious versions

1 flagged

1.0.73882

Indicators of compromise (SHA-256)

05bf71a48051c6800f72085d8d80f501dbb86f957e5d235188347df68bd717a5

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-07761

Credits

ReversingLabs · finder

Detect & block this

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