Which versions of bunldenr are malicious?

The following RubyGems versions of bunldenr are flagged malicious: 1.0.79738. Treat any of these as compromised.

How do I remediate bunldenr if I installed it?

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

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

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

Search your lockfiles and build artifacts for bunldenr (version 1.0.79738).

Malicious package

bunldenrRubyGems

Advisory published Sep 22, 2026Updated Sep 24, 2026

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

Malicious code in bunldenr (RubyGems)

MAL-2026-17053

Immediate action

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

gem uninstall bunldenr

Malicious versions

1 flagged

1.0.79738

Indicators of compromise (SHA-256)

2c6e2f9695b803a7288d5ff4f9d381be5cb7fab6b972f0261ac39f6c1c7f58c4

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-07739

Credits

ReversingLabs · finder

Detect & block this

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