Which versions of bunlddr are malicious?

The following RubyGems versions of bunlddr are flagged malicious: 1.0.46550. Treat any of these as compromised.

How do I remediate bunlddr if I installed it?

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

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

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

Search your lockfiles and build artifacts for bunlddr (version 1.0.46550).

Malicious package

bunlddrRubyGems

Advisory published Sep 22, 2026Updated Sep 24, 2026

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

Malicious code in bunlddr (RubyGems)

MAL-2026-17042

Immediate action

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

gem uninstall bunlddr

Malicious versions

1 flagged

1.0.46550

Indicators of compromise (SHA-256)

419c28b9104136964d1a0e9c33aa21ff07306a0bc2454929931c481ba3c72e3b

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-07728

Credits

ReversingLabs · finder

Detect & block this

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