Which versions of biuendler are malicious?

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

How do I remediate biuendler if I installed it?

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

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

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

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

Malicious package

biuendlerRubyGems

Advisory published Sep 22, 2026Updated Sep 24, 2026

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

Malicious code in biuendler (RubyGems)

MAL-2026-16618

Immediate action

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

gem uninstall biuendler

Malicious versions

2 flagged

1.0.01.0.22786

Indicators of compromise (SHA-256)

b4b0e4dc6b54bd5fb89ad23c96a3b9b1916cd89b1ee20f71ad0e947bcb988224

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-07282

Credits

ReversingLabs · finder

Detect & block this

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