Which versions of bunloder are malicious?

The following RubyGems versions of bunloder are flagged malicious: 1.0.96173. Treat any of these as compromised.

How do I remediate bunloder if I installed it?

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

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

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

Search your lockfiles and build artifacts for bunloder (version 1.0.96173).

Malicious package

bunloderRubyGems

Advisory published Sep 22, 2026Updated Sep 24, 2026

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

Malicious code in bunloder (RubyGems)

MAL-2026-17095

Immediate action

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

gem uninstall bunloder

Malicious versions

1 flagged

1.0.96173

Indicators of compromise (SHA-256)

dcec52bc421d52f2add21c8c4ce34dbb36f168e217f517194c11a8a737e2c20a

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-07781

Credits

ReversingLabs · finder

Detect & block this

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