Which versions of bunldera are malicious?

The following RubyGems versions of bunldera are flagged malicious: 1.0.19339. Treat any of these as compromised.

How do I remediate bunldera if I installed it?

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

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

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

Search your lockfiles and build artifacts for bunldera (version 1.0.19339).

Malicious package

bunlderaRubyGems

Advisory published Sep 22, 2026Updated Sep 24, 2026

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

Malicious code in bunldera (RubyGems)

MAL-2026-17060

Immediate action

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

gem uninstall bunldera

Malicious versions

1 flagged

1.0.19339

Indicators of compromise (SHA-256)

f52a58ae19426c322001b1b428561935480e841aad65776294a4f99745c90ab1

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-07746

Credits

ReversingLabs · finder

Detect & block this

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