Which versions of bunlder-rb are malicious?

The following RubyGems versions of bunlder-rb are flagged malicious: 1.0.42332. Treat any of these as compromised.

How do I remediate bunlder-rb if I installed it?

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

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

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

Search your lockfiles and build artifacts for bunlder-rb (version 1.0.42332).

Malicious package

bunlder-rbRubyGems

Advisory published Sep 22, 2026Updated Sep 24, 2026

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

Malicious code in bunlder-rb (RubyGems)

MAL-2026-17058

Immediate action

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

gem uninstall bunlder-rb

Malicious versions

1 flagged

1.0.42332

Indicators of compromise (SHA-256)

ad6320cf2c72ccde9b965e80229ba732e246a9e6e8a6ff9927fc8d4941b579eb

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-07744

Credits

ReversingLabs · finder

Detect & block this

O3 blocks bunlder-rb-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