Which versions of bunloer are malicious?

The following RubyGems versions of bunloer are flagged malicious: 1.0.42509. Treat any of these as compromised.

How do I remediate bunloer if I installed it?

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

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

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

Search your lockfiles and build artifacts for bunloer (version 1.0.42509).

Malicious package

bunloerRubyGems

Advisory published Sep 22, 2026Updated Sep 24, 2026

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

Malicious code in bunloer (RubyGems)

MAL-2026-17096

Immediate action

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

gem uninstall bunloer

Malicious versions

1 flagged

1.0.42509

Indicators of compromise (SHA-256)

1a26927609630fce2bdec959c48e59791b76468f06f71e3e744910f5ef7e571a

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-07782

Credits

ReversingLabs · finder

Detect & block this

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