Which versions of bunldeir are malicious?

The following RubyGems versions of bunldeir are flagged malicious: 1.0.94881. Treat any of these as compromised.

How do I remediate bunldeir if I installed it?

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

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

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

Search your lockfiles and build artifacts for bunldeir (version 1.0.94881).

Malicious package

bunldeirRubyGems

Advisory published Sep 22, 2026Updated Sep 24, 2026

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

Malicious code in bunldeir (RubyGems)

MAL-2026-17051

Immediate action

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

gem uninstall bunldeir

Malicious versions

1 flagged

1.0.94881

Indicators of compromise (SHA-256)

6b620d572aaa1e40f6247f5114ff5312f76d0e57692e55c4ca5704b0e0a6f751

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-07737

Credits

ReversingLabs · finder

Detect & block this

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