Which versions of bioundler are malicious?

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

How do I remediate bioundler if I installed it?

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

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

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

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

Malicious package

bioundlerRubyGems

Advisory published Sep 22, 2026Updated Sep 24, 2026

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

Malicious code in bioundler (RubyGems)

MAL-2026-16608

Immediate action

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

gem uninstall bioundler

Malicious versions

2 flagged

1.0.01.0.94815

Indicators of compromise (SHA-256)

9685367cd88ed17ec50e2af269ec34f4b45f672205fe0c88eff0bbfd8e4a4744

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-07270

Credits

ReversingLabs · finder

Detect & block this

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