Which versions of bunlader are malicious?

The following RubyGems versions of bunlader are flagged malicious: 1.0.0, 1.0.53260. Treat any of these as compromised.

How do I remediate bunlader if I installed it?

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

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

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

Search your lockfiles and build artifacts for bunlader (2 malicious versions).

Malicious package

bunladerRubyGems

Advisory published Sep 22, 2026Updated Sep 24, 2026

bunlader is a confirmed malicious RubyGems package (MAL-2026-17036) that executes malicious code on install (malicious versions 1.0.0, 1.0.53260). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in bunlader (RubyGems)

MAL-2026-17036

Immediate action

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

gem uninstall bunlader

Malicious versions

2 flagged

1.0.01.0.53260

Indicators of compromise (SHA-256)

7d0206fde468e4bc4af1d71ed4295472103765c1eadb4fda9e1ebc5ab86913e6

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-07722

Credits

ReversingLabs · finder

Detect & block this

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