Which versions of bunldelr are malicious?

The following RubyGems versions of bunldelr are flagged malicious: 1.0.93815. Treat any of these as compromised.

How do I remediate bunldelr if I installed it?

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

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

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

Search your lockfiles and build artifacts for bunldelr (version 1.0.93815).

Malicious package

bunldelrRubyGems

Advisory published Sep 22, 2026Updated Sep 24, 2026

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

Malicious code in bunldelr (RubyGems)

MAL-2026-17052

Immediate action

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

gem uninstall bunldelr

Malicious versions

1 flagged

1.0.93815

Indicators of compromise (SHA-256)

8b2e99c0b3159014841af9eeca9a8ce3bc6c7f5929555511f6c278adad3e790c

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-07738

Credits

ReversingLabs · finder

Detect & block this

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