Which versions of biuidler are malicious?

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

How do I remediate biuidler if I installed it?

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

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

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

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

Malicious package

biuidlerRubyGems

Advisory published Sep 22, 2026Updated Sep 24, 2026

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

Malicious code in biuidler (RubyGems)

MAL-2026-16620

Immediate action

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

gem uninstall biuidler

Malicious versions

2 flagged

1.0.01.0.52773

Indicators of compromise (SHA-256)

ef06c0b2119fef5062839512dd7c7e637fd93567992ea50a78d6a7527b28f7be

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-07284

Credits

ReversingLabs · finder

Detect & block this

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