Which versions of bunlderl are malicious?

The following RubyGems versions of bunlderl are flagged malicious: 1.0.85292. Treat any of these as compromised.

How do I remediate bunlderl if I installed it?

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

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

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

Search your lockfiles and build artifacts for bunlderl (version 1.0.85292).

Malicious package

bunlderlRubyGems

Advisory published Sep 22, 2026Updated Sep 24, 2026

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

Malicious code in bunlderl (RubyGems)

MAL-2026-17063

Immediate action

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

gem uninstall bunlderl

Malicious versions

1 flagged

1.0.85292

Indicators of compromise (SHA-256)

c6dc9646c2bd537468b4ef4aaee726884395140af2038def90b305221b9fe1d5

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-07749

Credits

ReversingLabs · finder

Detect & block this

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