Which versions of bunldero are malicious?

The following RubyGems versions of bunldero are flagged malicious: 1.0.48694. Treat any of these as compromised.

How do I remediate bunldero if I installed it?

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

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

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

Search your lockfiles and build artifacts for bunldero (version 1.0.48694).

Malicious package

bunlderoRubyGems

Advisory published Sep 22, 2026Updated Sep 24, 2026

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

Malicious code in bunldero (RubyGems)

MAL-2026-17065

Immediate action

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

gem uninstall bunldero

Malicious versions

1 flagged

1.0.48694

Indicators of compromise (SHA-256)

1d2187ba0707ee8f07f3d6d0d07be06e004932bb6aef7c74fd3a498298762646

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-07751

Credits

ReversingLabs · finder

Detect & block this

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