Which versions of biuedler are malicious?

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

How do I remediate biuedler if I installed it?

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

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

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

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

Malicious package

biuedlerRubyGems

Advisory published Sep 22, 2026Updated Sep 24, 2026

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

Malicious code in biuedler (RubyGems)

MAL-2026-16617

Immediate action

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

gem uninstall biuedler

Malicious versions

2 flagged

1.0.01.0.57239

Indicators of compromise (SHA-256)

7239956227158375e8b54b6d6737f18ff3f0e6926e4768d11c54e2be07e30021

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-07281

Credits

ReversingLabs · finder

Detect & block this

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