Which versions of bunleer are malicious?

The following RubyGems versions of bunleer are flagged malicious: 1.0.13048. Treat any of these as compromised.

How do I remediate bunleer if I installed it?

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

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

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

Search your lockfiles and build artifacts for bunleer (version 1.0.13048).

Malicious package

bunleerRubyGems

Advisory published Sep 22, 2026Updated Sep 24, 2026

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

Malicious code in bunleer (RubyGems)

MAL-2026-17087

Immediate action

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

gem uninstall bunleer

Malicious versions

1 flagged

1.0.13048

Indicators of compromise (SHA-256)

f5b19e120e409de8d32e40b75c9d64f05cce459600d6fbafc7a88f1ea9374178

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-07773

Credits

ReversingLabs · finder

Detect & block this

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