Which versions of bunldrr are malicious?

The following RubyGems versions of bunldrr are flagged malicious: 1.0.18931. Treat any of these as compromised.

How do I remediate bunldrr if I installed it?

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

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

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

Search your lockfiles and build artifacts for bunldrr (version 1.0.18931).

Malicious package

bunldrrRubyGems

Advisory published Sep 22, 2026Updated Sep 24, 2026

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

Malicious code in bunldrr (RubyGems)

MAL-2026-17080

Immediate action

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

gem uninstall bunldrr

Malicious versions

1 flagged

1.0.18931

Indicators of compromise (SHA-256)

c429b91f07e2ef60b293afa699d4ce06c6d1371ac03bdb0b1d0ba07c6b15ecb8

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-07766

Credits

ReversingLabs · finder

Detect & block this

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