Which versions of bunlnder are malicious?

The following RubyGems versions of bunlnder are flagged malicious: 1.0.52173. Treat any of these as compromised.

How do I remediate bunlnder if I installed it?

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

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

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

Search your lockfiles and build artifacts for bunlnder (version 1.0.52173).

Malicious package

bunlnderRubyGems

Advisory published Sep 22, 2026Updated Sep 24, 2026

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

Malicious code in bunlnder (RubyGems)

MAL-2026-17094

Immediate action

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

gem uninstall bunlnder

Malicious versions

1 flagged

1.0.52173

Indicators of compromise (SHA-256)

202027721c435b1c5b5edbcc7332ecc5325abbfb5397c26f338047f79ff49d12

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-07780

Credits

ReversingLabs · finder

Detect & block this

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