Which versions of bunldesr are malicious?

The following RubyGems versions of bunldesr are flagged malicious: 1.0.51389. Treat any of these as compromised.

How do I remediate bunldesr if I installed it?

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

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

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

Search your lockfiles and build artifacts for bunldesr (version 1.0.51389).

Malicious package

bunldesrRubyGems

Advisory published Sep 22, 2026Updated Sep 24, 2026

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

Malicious code in bunldesr (RubyGems)

MAL-2026-17068

Immediate action

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

gem uninstall bunldesr

Malicious versions

1 flagged

1.0.51389

Indicators of compromise (SHA-256)

3c9bdabbe5c89ec4c58379296784a465a773adee10807bcc570229989ae85069

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-07754

Credits

ReversingLabs · finder

Detect & block this

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