Which versions of biuadler are malicious?

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

How do I remediate biuadler if I installed it?

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

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

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

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

Malicious package

biuadlerRubyGems

Advisory published Sep 22, 2026Updated Sep 24, 2026

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

Malicious code in biuadler (RubyGems)

MAL-2026-16612

Immediate action

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

gem uninstall biuadler

Malicious versions

2 flagged

1.0.01.0.67462

Indicators of compromise (SHA-256)

4b2115c598035f4be967cd810ec7430ade46adb5c538b4d897f67a6d00852041

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-07276

Credits

ReversingLabs · finder

Detect & block this

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