Which versions of bunledr are malicious?

The following RubyGems versions of bunledr are flagged malicious: 1.0.96045. Treat any of these as compromised.

How do I remediate bunledr if I installed it?

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

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

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

Search your lockfiles and build artifacts for bunledr (version 1.0.96045).

Malicious package

bunledrRubyGems

Advisory published Sep 22, 2026Updated Sep 24, 2026

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

Malicious code in bunledr (RubyGems)

MAL-2026-17086

Immediate action

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

gem uninstall bunledr

Malicious versions

1 flagged

1.0.96045

Indicators of compromise (SHA-256)

3bdd5e266be395d3c9d40de8375497a6f68fa3e645b67437de19b5c8d63df8c3

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-07772

Credits

ReversingLabs · finder

Detect & block this

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