Which versions of bunldar are malicious?

The following RubyGems versions of bunldar are flagged malicious: 1.0.27847. Treat any of these as compromised.

How do I remediate bunldar if I installed it?

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

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

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

Search your lockfiles and build artifacts for bunldar (version 1.0.27847).

Malicious package

bunldarRubyGems

Advisory published Sep 22, 2026Updated Sep 24, 2026

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

Malicious code in bunldar (RubyGems)

MAL-2026-17040

Immediate action

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

gem uninstall bunldar

Malicious versions

1 flagged

1.0.27847

Indicators of compromise (SHA-256)

7a74175ccfef83706b4eba43d86b0d42ecba0f72c3e78f6b67261026a0e01291

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-07726

Credits

ReversingLabs · finder

Detect & block this

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