Which versions of buosndler are malicious?

The following RubyGems versions of buosndler are flagged malicious: 1.0.49497. Treat any of these as compromised.

How do I remediate buosndler if I installed it?

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

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

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

Search your lockfiles and build artifacts for buosndler (version 1.0.49497).

Malicious package

buosndlerRubyGems

Advisory published Sep 22, 2026Updated Sep 24, 2026

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

Malicious code in buosndler (RubyGems)

MAL-2026-17148

Immediate action

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

gem uninstall buosndler

Malicious versions

1 flagged

1.0.49497

Indicators of compromise (SHA-256)

bdf60b5294f10946faf13455a64109e257bee9ba03fea04ec98a0b72b278946c

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-07837

Credits

ReversingLabs · finder

Detect & block this

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