Which versions of bunlderi are malicious?

The following RubyGems versions of bunlderi are flagged malicious: 1.0.67493. Treat any of these as compromised.

How do I remediate bunlderi if I installed it?

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

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

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

Search your lockfiles and build artifacts for bunlderi (version 1.0.67493).

Malicious package

bunlderiRubyGems

Advisory published Sep 22, 2026Updated Sep 24, 2026

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

Malicious code in bunlderi (RubyGems)

MAL-2026-17062

Immediate action

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

gem uninstall bunlderi

Malicious versions

1 flagged

1.0.67493

Indicators of compromise (SHA-256)

d38033b888f8a3105ac4e15b2931d2f54011f7216d6488f51d138f41ab594b13

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-07748

Credits

ReversingLabs · finder

Detect & block this

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