Which versions of biuandler are malicious?

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

How do I remediate biuandler if I installed it?

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

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

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

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

Malicious package

biuandlerRubyGems

Advisory published Sep 22, 2026Updated Sep 24, 2026

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

Malicious code in biuandler (RubyGems)

MAL-2026-16613

Immediate action

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

gem uninstall biuandler

Malicious versions

2 flagged

1.0.01.0.9963

Indicators of compromise (SHA-256)

d44d63230924c5313697748616082c293afdf1fbb88e8a1e4277f2eb435b8dd6

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-07277

Credits

ReversingLabs · finder

Detect & block this

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