Which versions of biunedler are malicious?

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

How do I remediate biunedler if I installed it?

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

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

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

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

Malicious package

biunedlerRubyGems

Advisory published Sep 22, 2026Updated Sep 24, 2026

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

Malicious code in biunedler (RubyGems)

MAL-2026-16691

Immediate action

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

gem uninstall biunedler

Malicious versions

2 flagged

1.0.01.0.93894

Indicators of compromise (SHA-256)

d8b7eb83d7a56db80b57a4d39b80f7a5b13f3bb886861b7d46d01cbe37e6adea

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-07355

Credits

ReversingLabs · finder

Detect & block this

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