Which versions of bunldeor are malicious?

The following RubyGems versions of bunldeor are flagged malicious: 1.0.25151. Treat any of these as compromised.

How do I remediate bunldeor if I installed it?

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

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

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

Search your lockfiles and build artifacts for bunldeor (version 1.0.25151).

Malicious package

bunldeorRubyGems

Advisory published Sep 22, 2026Updated Sep 24, 2026

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

Malicious code in bunldeor (RubyGems)

MAL-2026-17055

Immediate action

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

gem uninstall bunldeor

Malicious versions

1 flagged

1.0.25151

Indicators of compromise (SHA-256)

ed257d0735c9b88479ecb05c87589d263859d669e2fec2055519fa0d9cfb21bf

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-07741

Credits

ReversingLabs · finder

Detect & block this

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