Which versions of biuondler are malicious?

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

How do I remediate biuondler if I installed it?

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

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

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

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

Malicious package

biuondlerRubyGems

Advisory published Sep 22, 2026Updated Sep 24, 2026

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

Malicious code in biuondler (RubyGems)

MAL-2026-16709

Immediate action

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

gem uninstall biuondler

Malicious versions

2 flagged

1.0.01.0.17676

Indicators of compromise (SHA-256)

5d0e8ed95d947557103a51dce5f7bbc213c89685fb68c675c8ea2b00038ec392

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-07373

Credits

ReversingLabs · finder

Detect & block this

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